← Camera index

● Manufacturer-documented path

Canon
EOS R5 Mark II

EOS R5 Mark II documents camera-initiated FTP/FTPS/SFTP transfer over built-in Wi-Fi, Ethernet via CF-R20EP. For Camera to Anywhere, configure a scoped input-gallery account and send JPEG, HEIF, RAW, movie files directly from the camera; downstream cloud and NAS routes run only after ingest is complete.

2024FTP · FTPS · SFTP

Direct camera client

TRANSPORT

built-in Wi-Fi + Ethernet via CF-R20EP

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

PAYLOAD

JPEG · HEIF · RAW · movie files

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

TRIGGER

new stills after capture / current still / selected or batch stills / movie files

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

STATUS

Documented.
Not lab-verified.

Some secure-protocol and wired options appear only with the CF-R20EP path; verify current firmware. 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

    A supported EOS R5 Mark II body or, for an accessory guide, a camera listed as compatible by Canon.

  2. 02

    No external transmitter is required for at least one documented network path; use only interfaces named in the manufacturer source.

  3. 03

    Current mutually compatible camera/transmitter firmware, a charged battery or continuous event power, and a writable memory card containing a supported file.

  4. 04

    A network path documented for this setup: built-in Wi-Fi, Ethernet via CF-R20EP.

  5. 05

    A Camera to Anywhere input gallery with a dedicated host, port, username, secret, destination directory, and any certificate or host-key data.

  6. 06

    A venue LAN or phone/dedicated hotspot without a captive-portal step on the camera and with outbound access to the configured FTP-family ports.

CONNECTION FIELDS

Protocol

The Camera to Anywhere profile choice supported by this body: FTP, FTPS, SFTP

The camera and ingest listener must use the same FTP-family protocol.

Server address / host name

The host name shown in the Camera to Anywhere input-gallery connection card; omit https:// and any path.

Camera FTP fields expect a server address, not a browser URL.

Port

The exact port published with the input-gallery credentials.

Camera to Anywhere may expose different listeners for FTP, explicit FTPS, or SFTP; do not assume a default.

Login name

The per-camera or per-job ingest username.

A scoped identity lets the gateway route and revoke one camera without changing every shooter.

Password / authentication secret

The generated secret shown once for this ingest identity.

The gateway rejects anonymous uploads and uses the credential envelope only for this input.

Target folder / directory

The destination path shown for the input gallery, including leading slash only when the connection card includes it.

The path is a routing key; changing its spelling can create a different server folder.

Passive mode

Use the passive-mode value shown by Camera to Anywhere; prefer passive when the camera offers it behind venue NAT.

Passive data connections are usually more compatible with hotspots and venue firewalls.

FTPS certificate / root certificate

Import or select the CA/root certificate specified by Camera to Anywhere when the camera manual requires certificate validation.

FTPS must authenticate the ingest endpoint before credentials and media are transmitted.

SFTP host key confirmation

Approve only the server fingerprint displayed by Camera to Anywhere.

Matching the host key prevents connecting to an impersonated SFTP endpoint.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Automatic: new stills after capture.
  • Manual: current still.
  • Manual: selected or batch stills.
  • Manual: movie files.
MEDIA BEHAVIOR
  • Still payloads documented by the manufacturer: JPEG, HEIF, RAW.
  • Video payloads documented by the manufacturer: movie files.
  • The camera writes the source file to its card first; Camera to Anywhere receives a transmitted copy and does not replace in-camera media management.
  • Treat the camera send mark as transport state, not cloud-delivery proof; confirm the asset appears in the Camera to Anywhere input gallery and destination activity log.
LIMITS + WARNINGS
  • Some secure-protocol and wired options appear only with the CF-R20EP path; verify current firmware.
  • Video or clip payloads require a manual selection unless the exact camera firmware manual states otherwise.
  • Venue Wi-Fi client isolation does not block a camera from reaching a public Camera to Anywhere host, but captive portals, outbound-port filtering, weak signal, and phone hotspot sleep can still prevent or interrupt transfer.
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. 01Confirm EOS R5 Mark II and every required transmitter/adapter run a compatible firmware combination.
  2. 02Create a dedicated Camera to Anywhere ingest identity for EOS R5 Mark II; do not reuse a destination OAuth token as a camera password.
  3. 03Match protocol (FTP/FTPS/SFTP), host, port, username, target directory, and passive/security options to the connection card.
  4. 04Send one small still or clip and wait for the camera transfer-complete mark.
  5. 05Verify the received file size and checksum in the Camera to Anywhere input gallery before enabling automatic or batch transfer.
  6. 06Test the exact recording codec/container and proxy setting planned for the event; a successful JPEG test does not prove video compatibility.
  7. 07Trigger the configured destination route and confirm its activity log independently from camera ingest.
  8. 08Lock the working camera profile against accidental edits and retain a second known-good profile or printed connection card for event recovery.
TROUBLESHOOTING

If it will not send,
start here.

01The camera cannot find or connect to the server

Confirm the camera has an IP address, the hotspot has Internet access, the host field contains no URL scheme/path, and the venue permits the published control and data ports.

02Login or destination-folder error

Re-enter the scoped username and secret, preserve case, and copy the target directory exactly; create a fresh ingest credential if the secret may have been exposed.

03Small files work but RAW or video stalls

Check remaining card space, battery/power, hotspot sleep settings, passive-mode configuration, signal strength, gateway size limits, and whether the camera permits that file type in the selected transfer mode.

04FTPS/SFTP security validation fails

Match the selected protocol and port, refresh the camera clock, reinstall the required CA certificate for FTPS, or verify the SFTP host fingerprint against the Camera to Anywhere connection card.

05The camera says sent but the destination does not show the asset

First verify the input gallery received the complete file, then inspect routing-node status; camera success covers the ingest hop, not Dropbox, NAS, or another downstream destination.

06Retries create duplicates or overwrite a prior file

Use a unique camera/job prefix and review the body manual overwrite/rename setting; Camera to Anywhere should deduplicate by upload identity and checksum rather than filename alone.

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

    Official manufacturer evidence

    Transferring Images to an FTP Server

    Open manufacturer source ↗
  2. 02

    Official manufacturer PDF archive source

    FTP transfer/network chapter corresponding to: Transferring Images to an 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 ↗