built-in 2.4/5 GHz Wi-Fi + built-in wired Ethernet LAN port
The documented network paths available to the camera or its required transmitter.
● Manufacturer-documented path
The GFX100 II initiates FTP, FTPS, or SFTP uploads without an external transmitter. It can use its built-in dual-band Wi-Fi or wired LAN port, save combined network/server profiles, upload selected stills or movies, and automatically order new captures for transfer.
Direct camera client
The documented network paths available to the camera or its required transmitter.
File behavior is quoted conservatively until a Camera to Anywhere fixture reproduces it.
Transfer can begin from the documented camera-side behavior shown here.
For FTPS, import and select the required root certificate. Use current camera firmware and revalidate the server profile after firmware changes. Physical Camera to Anywhere interoperability is not yet lab-verified.
Menu labels, behaviors, and warnings on this page are paraphrased from official manufacturer material.
Inspect every citation ↓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.
Current camera firmware.
A configured Wi-Fi network or Ethernet connection.
A memory card with a test JPEG.
Camera to Anywhere hostname, protocol, port, credentials, and remote directory.
The approved root certificate on the memory card when the FTPS endpoint requires a private or self-signed trust root.
Selects the endpoint security and transport behavior.
Identifies the upload server.
Must match the active ingress listener.
Most direct and hotspot connections do not use an FTP proxy.
Prevents dependence on an inbound data channel to the camera.
Authenticates and routes this camera's files.
Keeps this source isolated from other jobs.
Causes a numeric suffix instead of destructive replacement.
Enables TLS certificate validation.
Run this checklist on the exact body, firmware, network, and media format you will use on assignment.
Confirm the active profile uses the connected transport and that DHCP or static IP, gateway, and DNS values are valid.
Verify the server hostname, port, protocol, credentials, target folder, and venue firewall policy.
Load the correct root certificate and verify the endpoint hostname.
Turn on Auto Image Transfer Order and confirm the desired file type is enabled.
The local archive is retained for research continuity if an official link changes. It is not redistributed through this site.
Printed pp. 278-290, Uploading Files via FTP; printed pp. 326-327, FTP Optional Setting
Open manufacturer source ↗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.
Join the founding beta and help turn the documented route into a tested setup guide with original menu photography.
Test this path ↗