The Night Before the Wedding, I Taught My Camera to Send Photos by Itself

It was 10 pm, the night before Ananya and Rohit's wedding. My bags were packed, batteries charging in a neat row on the table.

And my camera was still a stranger to the internet.

The couple wanted guests to see photos during the reception, not a month later. So I made tea, sat at my desk, and decided to teach my camera one new trick: send photos by itself.

The setting I had ignored for years

Many Sony, Canon and Nikon bodies have it, buried in a menu. It's called FTP.

In plain words, FTP is the setting that lets a camera post each photo straight to a computer on the internet. That computer is called a server. Snapseek asks for the safer version, FTPS, which locks each photo in encryption while it travels.

Live FTPS is on the Pro and Business plans. If your camera has plain FTP but no FTPS/SFTP, don't worry. You can give it a phone instead.

Where Snapseek keeps the secret handshake

I opened the event on my Snapseek dashboard and went to the upload section. There was a button: Enable FTP Sync.

One tap, and the page showed four things my camera would need:

• FTP Host / Server: the address to send photos to
• Port: think of it as the door number at that address
• Username
• Password, with an eye icon to reveal it and a copy button

A gold note underneath said the important bit. The camera must use FTPS or Explicit TLS. Plain FTP is refused. And choose passive mode if the camera offers it.

Teaching the camera, one field at a time

Here is exactly what I did, sitting at the desk.

1. Turned on my phone's mobile hotspot and joined the camera to it from the camera's Wi-Fi settings. A hotspot is just your phone sharing its internet as a small Wi-Fi network.
2. Opened the camera's network / FTP menu. Every brand names it differently, so I kept the camera manual open on my laptop.
3. Typed in the host, port, username and password from the event page, slowly.
4. Set the security option to FTPS or Explicit TLS, and turned on passive mode.
5. Switched on the option to send photos automatically after each shot.
6. Ran the camera's own connection test, where the camera has one.
7. Took a photo of my tea mug.

Then I stared at the screen and waited.

The mug appears

Back on the Snapseek event page, the photo grid refreshed on its own. And there it was. A slightly blurry cup of tea, now living in the cloud.

The page checks for new photos every 15 seconds and shows when it last synced, so I didn't even have to press anything. I deleted the mug later. Nobody needed that at a wedding.

When it just won't talk

My first try failed. The camera kept saying it couldn't connect. Here's what I checked:

• Security type. If it's set to plain FTP, Snapseek won't accept it. Switch to FTPS or Explicit TLS.
• A typo. One wrong letter in the password is enough. Copy it again from the event page.
• The network. Is the camera actually on the hotspot? Does the phone have data?
• Passive mode. Turn it on if you skipped it.

If it still refuses, note your exact camera model and firmware version and ask Snapseek support. They can help with your specific body. And if your camera only offers plain FTP, with no FTPS/SFTP or Explicit TLS option, the Relay app is the other road.

Do it again at the venue

A desk test is good. A venue test is better.

If you do a recce, the visit to see the venue before the big day, take a few test shots there. Big halls and farmhouses can have weak mobile signal. Knowing that a day early is worth a lot.

Your own phone's hotspot is usually more dependable than venue Wi-Fi that 400 guests are also trying to use.

The next evening

At the reception, I clicked Rohit's grandmother dancing. Before the song ended, her granddaughter had found the photo with one selfie and was showing it around the table.

All because of one quiet cup of tea the night before.

If you'd like to see the whole journey from click to phone, read how camera-to-cloud works. Snapseek is there to keep that journey short for you and your guests.