OAuth without a bundled secret
The browser token flow uses a public client ID. No client secret is shipped in the bundle or stored on a server.
Workflow · Google DriveLocal-first
Google Drive Photo Import
Connect a read-only Drive account and pull photos straight into the local gallery.
Many photographers already keep deliveries and personal work in Drive. Instead of downloading a ZIP, extracting it, and uploading the files again, the Gallery can list Drive images and import the selected files directly into the local library.
Access uses Google Identity Services with the read-only Drive scope. The app ships no client secret: you provide a public OAuth web client ID for your own Google Cloud project, authorise this origin, and the short-lived token stays in memory.
No image uploads WebAssembly engine Works in the tab
What you can do
Google Drive, in detail.
Connect Google Drive to photos-assemb with a read-only OAuth token. Browse and search your Drive photos, download selected files, and edit them locally without a cloud editor.
Search Drive
List image files and common photography formats, sorted by modified time, with a filename search that queries the Drive API.
Select and import
Pick one or many files, watch per-file import progress, and land them in the same gallery used by local uploads.
Read-only by design
The app requests drive.readonly. It cannot rename, delete or upload files to your Drive.
Token handling
The access token lives in memory, expires on Google’s schedule, and is cleared when you disconnect or reload the page.
Then edit locally
Imported files are ordinary local gallery items. Open one in the editor or send a selection to batch processing.
How it works
From file to finish in three moves.
No install step and no import queue. Open the editor, work on the document locally, and export the file your next tool expects.
Try it now- 1
Create an OAuth client
In Google Cloud, enable the Drive API and create a Web application OAuth client. Add the current site origin to the authorised JavaScript origins.
- 2
Connect Drive
Paste the public client ID into the Drive dialog, sign in, and grant read-only Drive access.
- 3
Import and edit
Select files, import them into the gallery, then open or batch-edit them like any local photo.
Who it is for
Built for real photo work.
These are the workflows the tool is designed around — not a list of theoretical features.
- Pulling a client delivery from Drive onto a tablet for a quick edit.
- Importing personal photos from Drive without downloading a ZIP first.
- Working on a Chromebook or locked-down machine where installing a desktop app is not possible.
- Keeping the source library in Drive while doing the edit locally.
Questions
Google Drive FAQ
Straight answers about formats, privacy and limits.
Why do I need my own Google client ID?
Google requires every web app to identify itself with an OAuth client. The client ID is public, but it must be created in a Google Cloud project you control and authorised for this origin.
Can photos-assemb see my whole Drive?
With drive.readonly it can list and download files the authorised account can access. The app only requests the files you choose to import, and it cannot modify your Drive.
Where is the access token stored?
In memory for the current session. It is not written to localStorage or sent to a photos-assemb server. Disconnecting or reloading clears it.
Can I upload edited photos back to Drive?
No. The integration is read-only by design. Export the edited file and upload it with Drive’s own interface.
Put google drive to work.
Open the editor and bring a real file. Your photo stays on your device.