← Camera index

● Manufacturer-documented path

JVC
GY-HM660 / GY-HM660RE

The GY-HM660 and HM660RE can send completed clips over FTP, SFTP, implicit FTPS, or explicit FTPES through a supported HOST USB network adapter. Four Clip Server profiles, on-camera and browser selection, background transfer, and resumable FTP-family uploads make it suitable for destination-neutral field delivery.

2016FTP · 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.

The shared manual marks networking and FTP as HM660/HM660RE features, not HM620 features. Use current firmware; FTP resume is unavailable with SFTP. Physical Camera to Anywhere interoperability is not yet lab-verified.

MANUAL EVIDENCE

3 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-HM660/HM660RE firmware; the shared manual marks network features as HM660-family-only, not HM620.

  2. 02

    A JVC-supported HOST USB Wi-Fi, Ethernet, or cellular adapter.

  3. 03

    A recorded test clip.

  4. 04

    Camera to Anywhere endpoint host, protocol, port, credentials, and directory.

  5. 05

    Known SFTP/FTPS/FTPES server fingerprint.

CONNECTION FIELDS

Alias

Short Camera to Anywhere destination name.

Shown in the upload chooser.

Protocol

FTP, SFTP, FTPS (implicit), or FTPES (explicit); do not choose ZIXI for this integration.

Matches the open Camera to Anywhere listener.

Server

Hostname or IP without scheme/path.

Identifies ingress.

Port

Issued port; documented defaults are 21/22/990/21.

Connects to the matching listener.

Dir. Path

Assigned remote input path.

Routes the clip.

Username

Per-source username.

Authenticates and identifies the camera.

Password

Issued password.

Completes authentication.

PASV Mode

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

Uses a firewall-friendly passive data connection.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Single, selected, or all clips
  • Browser all/OK/selected upload
  • Background upload after returning to Camera mode
  • Resume an interrupted FTP/FTPS/FTPES transfer when the server supports append
MEDIA BEHAVIOR
  • Uploads completed playable clips from SD media.
  • Progress and stop controls are available.
  • Secure protocols require fingerprint verification.
  • A same-name smaller remote file is treated as a possible interrupted upload and can offer Resume.
  • Returning to Camera mode can allow shooting while transfer continues.
LIMITS + WARNINGS
  • Network/FTP functionality is not available on the HM620 bodies covered by the shared manual.
  • A supported HOST USB adapter is required.
  • Resume is disabled for SFTP and when an HTTP FTP proxy is selected.
  • Resume must target the partial copy of the same clip; otherwise skip or overwrite deliberately.
  • A server-side file-size limit should exceed 64 GB for the largest documented clip cases.
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 reports an IP.
  2. 02The correct Clip-FTP profile is selected.
  3. 03Secure fingerprint is verified.
  4. 04A short clip uploads with matching bytes.
  5. 05An interrupted non-SFTP test resumes only against its own partial file.
  6. 06A retry does not corrupt or silently replace another clip.
TROUBLESHOOTING

If it will not send,
start here.

01Cannot connect

Verify adapter, network addressing, Server, Port, and venue firewall.

02Authentication/path failure

Correct Username, Password, and Dir. Path in the selected profile.

03Resume is not offered

Confirm the protocol is not SFTP, no HTTP proxy is used, the server supports resume, and the same-name remote file is smaller.

04Secure protocol prompt

Verify the displayed fingerprint against the approved server value.

05Large clip fails

Remove restrictive server file-size quotas and retry on a stable network.

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 · 192 pages
  1. 01

    JVC GY-HM660/HM660RE Instructions

    Printed pp. 126-127, Clip Server; pp. 155-157, Uploading a Recorded Video Clip and FTP Resume

    Open manufacturer source ↗
  2. 02

    JVC online Clip Server settings

    Clip Server protocol and field definitions

    Open manufacturer source ↗
  3. 03

    JVC online FTP Resume Feature

    FTP Resume Feature

    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 ↗