← Camera index

Manufacturer-documented path

JVC
GY-HC500

The GY-HC500 can upload clips automatically, manually, or in HD+Web proxy chunks to destination-neutral FTP, SFTP, implicit FTPS, or explicit FTPES servers. Wired Ethernet is built in; supported HOST USB adapters add Wi-Fi or cellular connectivity. Four Clip Server profiles and resume support cover both rapid proxy delivery and full-clip handoff.

2019FTP · SFTP · FTPS implicit · FTPES explicit

Direct camera client

TRANSPORT

built-in wired Ethernet LAN + supported Wi-Fi adapter through HOST USB + supported cellular adapter 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

automatic upload after recording / automatic chunked upload during supported recording modes / manual clip upload / browser-triggered clip upload

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

STATUS

Documented.
Not lab-verified.

High-Speed recording disables clip FTP. Automatic chunked upload is limited to supported record configurations. 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-HC500 firmware.

  2. 02

    Built-in Ethernet or a supported HOST USB Wi-Fi/cellular adapter.

  3. 03

    A recorded test clip; HD+Web proxy configuration for chunk testing.

  4. 04

    Camera to Anywhere host, protocol, port, credentials, and destination path.

  5. 05

    Approved server fingerprint for a secure protocol.

CONNECTION FIELDS

Alias

Short job or destination label.

Identifies the profile in upload controls.

Protocol

FTP, SFTP, FTPS (implicit), or FTPES (explicit).

Matches the ingress listener.

Server

Hostname or IP without scheme/path.

Identifies Camera to Anywhere ingress.

Port

Exact assigned listener port.

Connects to the correct service.

Dir. Path

Assigned remote input directory.

Routes assets to the correct workflow.

Username

Per-camera/source username.

Authenticates and attributes the camera.

Password

Issued source password.

Completes authentication.

PASV Mode

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

Uses firewall-friendly passive data connections.

Slot / Server

The media slot and Clip-FTP alias monitored by Auto FTP.

Defines the automatic source and destination.

Division

15 seconds through 15 minutes, or Off, only for the approved HD+Web proxy workflow.

Controls the chunk cadence during recording.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Auto FTP after recording
  • HD+Web Slot-B proxy chunk upload during recording
  • Manual this/selected/all clips
  • Browser-triggered upload
  • Background transfer
  • Resume for interrupted FTP/FTPS/FTPES
MEDIA BEHAVIOR
  • Auto FTP watches the selected media slot.
  • Chunking splits and sends the Slot-B proxy while recording in HD+Web.
  • Manual mode exposes all playable clips in the thumbnail view.
  • Transfer status is visible on the status screen.
  • A smaller same-name remote file can offer Resume.
LIMITS + WARNINGS
  • Starting recording on the currently transferring auto-upload slot interrupts that transfer.
  • FTP does not run during live streaming or Return over IP.
  • High-Speed Record Format disables FTP transfer.
  • Chunked upload is limited to HD+Web proxy recording in Slot B.
  • Resume is unavailable for SFTP and HTTP FTP proxy operation.
  • Wi-Fi/cellular requires a supported HOST USB adapter; built-in connectivity is wired Ethernet.
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 the correct transport and IP.
  2. 02Profile and secure fingerprint are verified.
  3. 03Manual clip bytes match remotely.
  4. 04Auto FTP sends a newly completed clip.
  5. 05Required HD+Web chunk cadence is verified end to end.
  6. 06Slot conflict, streaming, high-speed, and resume behaviors are captured in the runbook.
TROUBLESHOOTING

If it will not send,
start here.

01Auto FTP does not begin

Set Upload to Auto, select Slot and Server, turn Auto Upload On, and leave High-Speed mode.

02Upload is interrupted by recording

Record to a different slot from the one configured for auto FTP.

03No chunks arrive

Use System HD+Web, proxy Slot B, Division not Off, and Auto Upload On.

04Server/login/path error

Verify Server, Port, Protocol, Username, Password, Dir. Path, and account permissions.

05Resume unavailable

Confirm a resume-capable non-SFTP endpoint, no HTTP proxy, and a valid smaller partial file.

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

    JVC GY-HC500/GY-HC550 Instructions

    Printed pp. 148-150, Upload Settings and Clip Server; pp. 189-193, Auto FTP, chunked upload, Manual FTP, and Resume

    Open manufacturer source ↗
  2. 02

    JVC online Auto FTP

    Uploading Clips Automatically (Auto FTP)

    Open manufacturer source ↗
  3. 03

    JVC online Automatic Chunked Upload

    Automatic Chunked Upload to FTP Server

    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