← Camera index

● Manufacturer-documented path

JVC
GY-HM650

The GY-HM650 uploads completed SD-card video clips to any configured FTP, SFTP, implicit FTPS, or explicit FTPES server. A supported Wi-Fi, Ethernet, or cellular adapter connects through the rear HOST USB port; the camera can upload from its thumbnail screen or from its browser interface.

2012FTP · SFTP · FTPS implicit · FTPES explicit

Accessory-assisted camera client

TRANSPORT

Wi-Fi adapter through HOST USB + Ethernet adapter through HOST USB + cellular modem through HOST USB

The documented network paths available to the camera or its required transmitter.

PAYLOAD

recorded video clips on SD media

File behavior is quoted conservatively until a Camera to Anywhere fixture reproduces it.

TRIGGER

manual clip upload from thumbnail view / selected or all-clip upload / browser-triggered clip upload

Transfer can begin from the documented camera-side behavior shown here.

STATUS

Documented.
Not lab-verified.

Use the current firmware and JVC's current supported-adapter list. FTP resume is unavailable when SFTP is selected. Physical Camera to Anywhere interoperability is not yet lab-verified.

MANUAL EVIDENCE

2 cited locations

Menu labels, behaviors, and warnings on this page are paraphrased from official manufacturer material.

Inspect every citation ↓
BEFORE YOU TOUCH THE MENU

Prepare the camera.
Prepare the route.

Gather these items first, then enter the Camera to Anywhere job credential exactly as issued. The camera sends to the public ingest edge; your private destinations stay downstream.

PREREQUISITES
  1. 01

    Current GY-HM650 firmware.

  2. 02

    A JVC-supported USB Wi-Fi, wired-LAN, or cellular adapter for the intended transport.

  3. 03

    A recorded test clip on supported SD media.

  4. 04

    Camera to Anywhere hostname, protocol, port, username, password, and remote directory.

  5. 05

    The known server public-key or certificate fingerprint for the first SFTP/FTPS/FTPES connection.

CONNECTION FIELDS

Alias

A short recognizable name such as C2A-Event-A.

This is the destination name shown in the FTP Upload action screen.

Protocol

FTP, SFTP, FTPS for implicit TLS, or FTPES for explicit TLS.

Must exactly match the Camera to Anywhere listener.

Server

The hostname or IP address only, up to the camera's documented 127-character limit.

Identifies the upload server.

Port

The issued port; documented defaults are FTP 21, SFTP 22, FTPS 990, and FTPES 21.

Connects to the correct protocol listener.

Dir. Path

The assigned remote directory such as /event/source.

Routes clips to the correct input.

Username

The per-camera/source username, within the documented 31-character limit.

Authenticates and identifies the source.

Password

The issued password, within the documented 31-character limit.

Completes endpoint authentication.

PASV Mode

On for ordinary FTP/FTPS/FTPES behind NAT; it is unavailable for SFTP.

Uses a firewall-friendly passive FTP data connection.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • This Clip from the thumbnail screen
  • Multiple selected clips
  • All playable clips
  • Browser upload of all, OK-marked, or selected clips
  • Background continuation after switching back to Camera mode
MEDIA BEHAVIOR
  • The upload unit is a completed recorded clip on SD media, not a live camera feed.
  • All playable clips visible in the active thumbnail context can be selected.
  • Upload progress is shown by a bar; the transfer can be stopped from the upload screen.
  • The camera can return to Camera mode and shoot while an existing upload continues.
  • A duplicate remote filename prompts for overwrite unless an HTTP FTP proxy suppresses the prompt.
LIMITS + WARNINGS
  • A supported USB network adapter is required for every transport.
  • The manual does not document automatic upload-after-record or chunked upload for this model.
  • Secure protocols prompt for server fingerprint validation; production staff need the expected value in advance.
  • An HTTP FTP proxy permits only FTP and can overwrite a duplicate without the normal confirmation.
  • This manual revision does not document resume; plan a full re-upload after interruption.
FIELD VERIFICATION

Prove the path before the green flag.

Run this checklist on the exact body, firmware, network, and media format you will use on assignment.

  1. 01Network status shows an IP address.
  2. 02Clip Server alias contains the intended host, port, protocol, and path.
  3. 03The displayed secure-protocol fingerprint matches the approved value.
  4. 04One short clip uploads successfully.
  5. 05Remote filename and byte size match the SD-card clip.
  6. 06A stopped/failed transfer can be retried without overwriting an unrelated file.
TROUBLESHOOTING

If it will not send,
start here.

01Cannot Connect to Server

Verify Server and Port, adapter/network status, DNS, gateway, and outbound venue rules.

02Invalid Username or Password

Re-enter the exact source credentials in the selected Clip-FTP profile.

03Invalid Path Was Requested

Correct Dir. Path and confirm the server account can create/write there.

04Adapter Was Removed

Reconnect the supported HOST adapter and repeat the transfer.

05Transfer timeout or error

Retry on a stable network, verify the server is reachable, and inspect the camera's FTP error screen.

PRIMARY EVIDENCE

Official source trail.

The local archive is retained for research continuity if an official link changes. It is not redistributed through this site.

archived-local-ignored · retrieved 2026-08-26 · 188 pages
  1. 01

    JVC GY-HM650 Instructions

    Printed pp. 124-125, Clip Server; pp. 152-153, Uploading a Recorded Video Clip; pp. 160-162, browser upload

    Open manufacturer source ↗
  2. 02

    JVC online Configuring the FTP Server for Uploading

    Configuring the FTP Server for Uploading

    Open manufacturer source ↗
BEFORE FIELD USE

Documentation gets us to the menu. Hardware earns the badge.

This guide compiles all discovered FTP-related setup evidence for this model, but it is not a promise that every firmware version and venue network will behave identically. Verification records the exact body, firmware, access point, protocol, payload, and result.

Have this camera?

Join the founding beta and help turn the documented route into a tested setup guide with original menu photography.

Test this path ↗