← Camera index

● Manufacturer-documented path

Sony
ILCE-7CR (Alpha 7CR)

ILCE-7CR (Alpha 7CR) can initiate FTP, FTPES transfer of still images, original movies, proxy movies over Wi-Fi infrastructure/hotspot; USB-to-Ethernet; USB tethering. The documented route accepts a user-configured server; it is suitable for a destination-neutral ingest gateway after protocol, firmware, and payload testing.

2023FTP · FTPES

Accessory-assisted camera client

TRANSPORT

Wi-Fi infrastructure/hotspot + USB-to-Ethernet + USB tethering

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

PAYLOAD

still images · original movies · proxy movies

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

TRIGGER

one-image, batch, and automatic/background transfer

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

STATUS

Documented.
Not lab-verified.

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

    Use a network route supported by this body: Wi-Fi infrastructure/hotspot; USB-to-Ethernet; USB tethering.

  2. 02

    Have the required hardware ready: none for Wi-Fi; commercial USB-to-LAN adapter for Ethernet; USB cable and phone for USB tethering.

  3. 03

    Prepare a reachable FTP, FTPES server account, destination directory, and test file permissions before entering the field.

  4. 04

    For FTPES/secure FTP, obtain the issuing CA root certificate in the format accepted by the camera and verify the server certificate chain.

CONNECTION FIELDS

Display Name

A short human-readable label such as Camera to Anywhere Event A.

Lets the operator identify the correct saved destination under pressure.

Host Name

The public DNS name or reachable IP address supplied for the ingest endpoint; do not include a web URL path.

The camera opens its FTP-family connection to this host.

Secure Protocol

Select one of the modes the body documents: FTP, FTPES.

This determines whether credentials and media use plain FTP, TLS, or SSH protection.

Port

The endpoint port supplied with the ingest credentials; use the server value rather than assuming a default.

Camera and server must agree on the listening service.

User / Password

A camera-specific, least-privilege ingest credential.

Separating credentials per camera supports revocation and attribution.

Specify Directory

The remote inbox path assigned to this camera or event.

Keeps simultaneous bodies and clients isolated at ingest.

Passive Mode

Use the mode required by the server/firewall; passive is normally the workable choice behind venue NAT.

FTP data connections fail when the server and NAT/firewall expectations do not match.

Root Certificate / certificate-error policy

Import the trusted CA root and leave certificate validation enabled for production.

FTPES verifies that the camera reached the intended server.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Manual transfer is supported: one-image, batch, and automatic/background transfer.
  • Automatic/background transfer is documented for this firmware-qualified path; test whether it runs during the chosen shooting and playback state.
  • Use a small one-image transfer first, then a batch or automatic rule only after the endpoint reports a complete file.
MEDIA BEHAVIOR
  • Documented payload classes: still images, original movies, proxy movies.
  • When the menu offers original/proxy or file-type selection, explicitly choose the desired payload rather than relying on the prior job setting.
  • A movie transfer can be much larger than a still-image transfer; verify media and battery headroom before enabling an automatic rule.
LIMITS + WARNINGS
  • Network routes are limited to: Wi-Fi infrastructure/hotspot; USB-to-Ethernet; USB tethering.
  • Plain FTP does not encrypt credentials or media; expose it only through a controlled gateway and prefer FTPES or SFTP when the body supports them.
  • Menu wording and available filters can change with camera firmware; use the guide matching the installed system-software version.
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. 01Send one small still or proxy to the assigned inbox.
  2. 02Confirm the server records the expected camera credential and target directory.
  3. 03Compare the received file size with the camera/media listing and open the file.
  4. 04Power-cycle or reconnect the camera, then confirm the saved server slot still targets the intended endpoint.
  5. 05If automatic transfer is enabled, make one new recording and verify it arrives without a manual selection.
TROUBLESHOOTING

If it will not send,
start here.

01The server slot will not connect.

Confirm network link, DNS, endpoint reachability, protocol/port pairing, and that the account is allowed from the camera network.

02FTPES fails before login.

Verify camera date/time, CA root import, certificate hostname, TLS compatibility, and certificate-error setting.

03Login succeeds but files do not arrive.

Check the remote directory spelling, user write permission, filename collision policy, media selection, and free space.

04Automatic transfer does not start.

Confirm FTP Function is On, the intended server is selected, the auto/background mode is enabled, and the current recording mode permits transfer.

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-official-pdf · retrieved 2026-08-26T04:40:28Z · 28 pages
  1. 01

    Official model or firmware evidence

    What you can do with the FTP transfer function

    Open manufacturer source ↗
  2. 02

    Official manufacturer PDF

    What you can do with the FTP transfer function

    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 ↗