Chrome Storage Vs IndexedDB
Close Chrome, reopen it, and your download tasks are still there. Where did they live while the browser was closed? Extensions use more than one on-device storage system. Understanding chrome storage vs IndexedDB explains why your settings persist and where uploaded files actually sit.
Inside the Chrome extension, preview, filter, and export stay together — no jumping between tabs and desktop tools.
Bulk Image Downloader From URL List stores data locally in your browser—not on a remote account server for task lists.
Step 1: what chrome.storage.local is for
chrome.storage.local is the Chrome extension API for structured key-value data. It is fast to read and write, persists across browser restarts, and suits configuration-sized payloads. In this extension it holds:
- download task definitions and URL lists
- per-task settings (filters, ZIP toggle, convert/resize options, IF-URL rules)
- Saved Rules with scraper filter presets
- global options like parallel download count and queued-download mode
- duplicate-finder hash cache entries
Think of it as the filing cabinet for settings and lists you touch constantly.
Step 2: what IndexedDB is for
IndexedDB is a browser database built for larger records, including binary blobs. the extension uses it for Upload Mode files—local images you drag into a task for processing. Storing multi-megabyte binaries in chrome.storage would be slow and awkward; IndexedDB is the right shape for file payloads.
Step 3: compare the two side by side
| Factor | chrome.storage.local | IndexedDB |
|---|---|---|
| Typical data | Tasks, URL lists, settings | Uploaded local image files |
| Size profile | Small structured JSON | Larger binary blobs |
| CSV export | Task settings export via Export Tasks (all tiers) | Upload-mode files not portable in CSV |
| Best at | Frequent reads/writes of config | Storing file content locally |
Neither storage type is “better” universally—each matches a different job. Some UI preferences (such as watermark preview state) may also use localStorage in the watermark tool.
Step 4: how this maps to privacy and backups
Task data stays on your machine in browser storage APIs. License authentication uses separate auth data—your URL collections are not uploaded for account lookups.
Because tasks live locally, Export Tasks CSV is your portable backup of settings and URL lists. Licensed PRO supports bulk CSV import to restore large packages. Uploaded IndexedDB files are not included in that CSV; re-add local uploads after a browser reset if you rely on Upload Mode.
Step 5: what to do in practice
- export task CSV periodically if tasks matter to your workflow
- remember URL-list tasks survive restarts via chrome.storage.local
- do not expect Upload Mode binaries to round-trip through CSV
- treat local storage as device-bound, not cloud-synced
Install the extension knowing where tasks versus uploaded files live makes backups and troubleshooting clearer.
For a broader comparison, see our roundup of best bulk image downloader extensions.
What the export can and cannot move
Export all downloads writes a CSV you can open in a spreadsheet, and Export Tasks produces a task backup. Those cover setup, not the files themselves. Downloads, drafts, and AI files stay on this computer, and the extension does not record what you download; signing in only checks your license.
That split explains where a CSV fits. It moves configuration between tasks or machines, but it does not carry the saved pictures. Restoring from a CSV rebuilds what a task should do; it does not restore the output of a previous run. Clearing local data in the current profile removes the files, while Incognito and other profiles keep their own copies.
Continue reading: Complete Bulk Image Download.