Google Photos Picker Limits and Batching: What to Expect
Learn how the Google Photos Picker limit works, when to use Pick More, and how to handle larger exports in batches.
Tested against the current IMGLoader workflow and provider UI available as of March 29, 2026. Where platform rules or API limits affect results, this guide calls them out explicitly.
Google Photos Picker is intentionally scoped. IMGLoader does not enumerate your entire Google Photos library in the background; it works from the explicit selection you make through Google Photos Picker itself. That is better for privacy, but it also means you need a batching strategy when the job is larger than a single picker session.
The important limit is straightforward: the picker session is capped at up to 2,000 selected items. The correct response is not to force it harder. It is to add batches deliberately with Pick More.
How the first batch should work
Connect Google Photos, click Pick from Google Photos, and make your first selection inside the Google picker. Think of that first selection as a working batch, not as a vague starting point.
That usually means grouping by album, time period, event, or project instead of selecting thousands of mixed photos with no verification step.
How to extend the export with Pick More
After the first selection is loaded into IMGLoader, use Pick More to open another picker session and add the next batch. This is the intended flow for large exports.
Using batches also makes mistakes cheaper. If you realize the previous selection was too broad or too narrow, you only have to revisit that batch, not an entire all-or-nothing export.
Practical batching rules that work well
- Batch by album, time period, event, or folder destination so each ZIP still has a clear purpose.
- Confirm the first batch count before adding another one.
- Do not wait until the end to notice you selected the wrong account or wrong slice of the library.
- If you are exporting for migration, mirror the destination grouping in your batch names.
Why this limit exists
The 2,000-item ceiling comes from the picker session configuration, not from arbitrary IMGLoader UI friction. The workflow is intentionally based on explicit user selection through the provider interface rather than broad hidden access to your library.