Ownership

Every guest photo,straight to your Google Drive.

Glint sends every guest photo and video straight into your own Google Drive, and never stores the files itself. Guests scan a QR code or tap a link, upload from their phone’s browser with no app and no login, and each original lands in one folder for your event, at full resolution, yours to keep forever.

A Google Drive folder filling with wedding photos and videos from guests
Why it matters

The photos of your wedding should not live in someone else’s app. They should live where you can always reach them, in storage that answers to you and no one else.

Most ways of gathering guest photos quietly take custody of them. A closed gallery app holds your pictures inside its own walls, and the day you stop paying, or the day it shuts down, your album can go with it. We built Glint the other way around. The files never belong to us, because they never pass through us. They go directly into the Google Drive you already have, and they simply stay there.

It is the same idea behind the easiest way to collect wedding photos from a hundred guests at once: ask as little as possible of them, and keep everything they send in one place you own.

Set it up

Three steps, thenyou just watch

There is nothing to install and nothing for your guests to learn. You connect Drive once, share one code, and the photos start arriving on their own.

01

Connect your Drive once

Sign in as the host and link your Google Drive in a single tap. Glint creates one folder for your event and asks for nothing beyond it. This is the only Google step in the whole process, and only you ever take it.

02

Share your QR code or link

Glint gives you a designable QR code and a short link for the event. Print it on a table card, add it to the invitation, or drop it in the group chat. Guests scan or tap, and the upload page opens.

03

Photos land in your folder

Each guest uploads straight from their phone browser, with no app and no login. Every original files itself into your event folder, named by date and guest, the moment it arrives, and you watch the folder fill in real time.

How it works

Straight to your Drive,and only yours

The path is short by design. You connect Drive once. Guests upload. The files land. Here is what that means for who holds your memories, and who can see them.

01

Where do the photos actually land?

In a folder Glint creates inside your Google Drive, one per event. Every guest upload files itself there as it arrives, named by date and guest, so you open Drive after the wedding to a tidy album, not a chase across camera rolls.

02

Who holds the files: you, or us?

You do, and only you. The upload travels from the guest's phone to your Drive directly. Glint keeps the guest's name and the file's name, never the file itself, so there is no Glint copy to lose, leak, or hold over you.

03

How does the connection stay safe?

Glint asks for one of the narrowest Google permissions there is: the kind limited to folders the app creates. It can drop your guests' photos into the event folder and nothing more. The rest of your Drive, your documents, your other photos, stays entirely out of view.

04

What happens after the wedding?

Nothing you need to do. The originals are already in your Drive at full resolution, up to 500 MB a file. No export, no download deadline, no service to keep paying so your memories survive. They are simply yours, forever.

The manual method

The DIY Drive + QR hack,and where it breaks

You can gather guest photos with nothing but a Google Drive folder and a free QR code, and for a small, tech-comfortable crowd it can be enough. It is worth knowing exactly how the hack works, and exactly where it starts to strain, before you trust one wedding to it.

The setup is straightforward. Create a folder in your Google Drive, open its sharing settings and switch the link to “Anyone with the link” as an Editor so people can add files, then paste that link into any free QR generator and print the code for your tables. Scan it, and the folder opens. The trouble is that a shared Drive folder was built for a handful of collaborators you trust, not a hundred guests uploading once from their phones, and that shows up fast.

Where it breaksA DIY Drive folder + QRThe Glint fix
Guests hit a sign-in wallAdding files to a shared Drive folder needs a Google account, signed in on that phone.No Google account, no login. Guests upload from any phone browser.
Everyone can edit everythingIn an editable shared folder, guests can open, and remove, each other’s files.Each guest sees only their own upload screen; no one can browse or delete the collection.
Everything lands in one pileFiles arrive mixed together, named by whatever each phone called them.Filed by date and guest in your event folder as each one lands.
No way to see it fillingYou refresh the folder and hope the uploads are coming in.A live dashboard shows every upload the moment it arrives.
Big videos are fragileA dropped signal mid-upload can mean starting the whole file again.4 MB resumable chunks, retried up to four times, resuming from the last byte.

None of this is a flaw in Google Drive. It is simply the difference between a tool for trusted collaborators and a tool built for one night of a hundred guests. Glint keeps the part you liked about the hack, the QR code and your own Drive, and quietly fixes the rest.

The difference

Your Drive, versusa closed gallery app

A shared Drive folder sounds like the obvious answer, until a guest opens it and meets a sign-in prompt and gives up. A Google Photos shared album is smoother, but it can quietly compress your originals and blends them into your own library. A closed gallery app removes the friction and takes the photos in exchange. Glint keeps the easy upload and leaves full-resolution ownership with you.

 Glint to your DriveShared Drive folderGoogle Photos shared albumClosed gallery app
Who stores the filesYour Google DriveYour Google DriveGoogle’s cloud, in your PhotosThe app’s servers
File qualityFull-resolution originalsFull resolutionCan be compressed by Google PhotosOften re-compressed
Who owns themYou, from upload oneYouYou, but mixed into your libraryHeld inside the app
Guest effortScan and upload, no loginOpen link, then often sign inUsually needs a Google accountVaries, sometimes an account
After the eventYours forever, in DriveYours, but guests can edit the folderYours, blended with your personal photosGone if you stop paying

The full picture of how the uploads, the QR code, and the live dashboard fit together is on the features page. The short version: guests get the simplest possible upload, and you get to keep what they send.

What we can see

Built to seeas little as possible

drive.fileThe only Drive scope we useOne of the most limited permissions Google offers. Glint can see only the folder it creates for your event, and never the rest of your Drive.
AES-256How your connection is storedThe tokens that link your Drive are encrypted at rest with AES-256, so the keys to your folder are never left in the open.
0 filesWhat we keep on our serversGlint stores metadata only, the guest’s first name and the file’s name. The photos and videos themselves never touch a Glint server.
After the wedding

Yours to download,back up, and share

Everything is already in your Drive at full resolution, so the morning after the wedding there is no export to run and no download deadline to beat.

Download the whole folder in one go for a copy on your own machine, back it up wherever you keep what matters, and share the folder straight from Google Drive so parents and friends get the originals too. None of it depends on Glint still being around, because the files were never ours to begin with.

Compare

Weighing your options? See the honest 2026 comparison of wedding photo apps, or how Glint stacks up against another Drive-first tool in Glint vs WedUploader.

Questions

Common questions

The answers below cover where the files live, what we can see, and what happens after the day. For the current plans, see the pricing page.

Your photos,in your own Drive.

Straight to your Google Drive. Glint stores nothing.