SnapMonkey for photographers

The setup, end to end, on one shoot day

Concrete steps, in order:

1. Pre-shoot, at the office. Open the SnapMonkey dashboard. The "Camera credentials" pane gives you an FTP host, a port, a username, and a password. Each second-shooter (or each camera if you want per-body folder routing) gets its own credential set; one camera per credential makes the post-shoot organization trivial. Authorize Google Drive — that's the one-time OAuth — and pick a destination folder like Shoots/2026-05-19-Smith-Wedding/Lead/.

2. In the field, before the first frame. Walk to the camera. Menu → Communication settings → Network settings → Transfer images to FTP server. Paste the host, port, username, password. Save the configuration as SnapMonkey. Take one test shot. Within 5–10 seconds the SnapMonkey dashboard shows the thumbnail and a "delivered" status; the frame is in Google Drive.

3. Shoot. No further interaction. Every frame the camera writes during the ceremony, the reception, the formals, flows through SnapMonkey to the cloud folder. The lead body writes to Lead/; the second-shooter's body writes to Second/. The transfer log timestamps every frame so when the client asks "I never got photo 472," you have a delivery receipt.

4. Drive home. Lightroom on your laptop is already pulling the cloud folder in the background. By the time you reach the desk, the cull set is staged. No SD-card-to-laptop ferry. No "did I import that card already" archaeology Tuesday at 11 pm.

The multi-body, second-shooter case (where this actually pays off)

The workflow above for one body is convenient. The workflow with three bodies — lead, second, detail — is where the workflow turns into operating leverage.

Each body gets its own SnapMonkey credential and its own destination folder. The lead body writes to Lead/; the second-shooter's R5 writes to Second/; the detail R6 II on the table-and-rings shots writes to Detail/. By the time you and the second-shooter compare notes after the ceremony, both your sets are already on the shared Drive, side by side. The cull conversation can happen on the drive home instead of three days later when the laptops finally meet up.

If a card fails mid-day — and they do, especially on the older bodies — the frames transmitted before the failure are still in the cloud. You lose what hadn't transmitted yet, not the whole card.

When the WiFi dies

SnapMonkey transmits over the camera's WiFi radio. No WiFi, no transmission. The honest shape:

Most venues have WiFi. Hotels, country clubs, restored barns with electricity, anywhere the venue itself runs a bar or POS. Connect the camera to the venue's guest network and the workflow runs as designed.

Where it doesn't, a phone hotspot covers most of it. The Canon EOS bodies all support connecting to a mobile hotspot. 20 MB / minute is enough headroom for typical event-photography write rates; data usage is high but tolerable for a 6–8-hour event on most consumer plans.

When neither exists, the frames still land on the card. Outdoor weddings in remote venues, off-grid environmental portraiture, anything in a basement-of-a-church zone with no cell signal — the frames write to the SD card as they always have. The real-time value isn't there, but you haven't lost anything. Import from card when you get back; the workflow reverts to the pre-SnapMonkey shape for that one shoot.

It's worth saying clearly: SnapMonkey is most useful when there's connectivity, and least useful when there isn't. The Canon FTP feature is built around that same assumption — SnapMonkey doesn't change the trade-off, it removes the server-ownership tax that kept photographers from using the feature their camera already had.

When this isn't the right fit for a photographer

You don't shoot Canon. SnapMonkey today is Canon-only — specifically the R-series mirrorless and the pro DSLRs whose WiFi menu carries "Transfer images to FTP server." We don't have a roadmap to add Sony, Nikon, or Fujifilm; the focused Canon experience is what lets the setup stay one screen.

You shoot exclusively tethered. If your workflow is "camera plugged into a laptop with EOS Utility running the whole time," your file-routing is already deterministic. SnapMonkey's pitch is specifically the untethered case.

You shoot fewer than 200 frames a month. The free plan covers 200 transfers monthly. Below that, the value proposition is thin — wait until shoot volume justifies the setup time.

You shoot somewhere with no WiFi and no cell coverage. See the WiFi block above. Outdoor remote venues with no connectivity won't see the real-time benefit; the workflow reverts to card-based import for those specific shoots.