Exporting

Renamerly never modifies files on disk. Every export is a fresh ZIP file generated client-side and downloaded through your browser.

Full-session ZIP

Click Export in the top-right of the workspace. Every row whose active filename format renders to a non-empty filename is included. Inbox rows and rows missing a value for a required token ({sku}, {descriptor}, or {group} when the format references them) are skipped silently.

Each file is:

1. Read from the browser's File handle.
2. Streamed into JSZip with its freshly generated filename.
3. Emitted into a single ZIP named after the current session (untitled-session.zip by default; rename the session in the sidebar to change it).

The ZIP also includes a manifest.csv row-for-row listing the original filename, new filename, every metadata value (sku, descriptor, group, and any custom keys), and alt text (if generated). Useful for downstream CMS uploads that want to cross-reference original filenames.

Exporting while at the Free cap

Free users at the 20-image session cap can still export. The cap affects only how many images the workspace holds simultaneously — it does not gate the export button.

Why does the export button sometimes say "2 images skipped"?

Two categories of skip:

• Missing required token value — when the active format references {sku}, {descriptor}, or {group} and the row has no value for the referenced key. The row is skipped with a warning toast. Fix by editing the row inline or via Set Metadata in the selection toolbar, then re-exporting.
• Unreadable File handle — after a Stripe return or a browser tab that was suspended. The session-restore defence auto-drops these on load, but a race can still skip one or two. Re-drop the affected files and try again.

What about exporting to a cloud destination?

Direct upload to Shopify / Etsy / S3 / Dropbox is on the roadmap but not shipped. The current flow is: download ZIP → extract locally → drag into your destination's media upload.

A signed-URL upload destination per template is the leading candidate for the first cloud integration. Track it in the product changelog.