Every paid or credit-backed Generate on Rhinobird should end with files you can ship to ads, marketplaces, or clients. History is that handoff point: a signed-in library of past runs with previews and downloads. This article explains how to open History on the English UI, what to do when the list is empty, and how to retrieve assets without re-running generation.
Open History
Two equivalent entries exist on the international site:
- Click History in the sidebar (alongside AI Assistant, Packaging, and Inspiration).
- Navigate directly to the generation history route when you are already signed in.
History is account-scoped. If you are not signed in, complete Login / Sign up first—Continue with Google or Continue with Email on the international site—then return to History.
Understand the list view
Each completed run typically appears as a card with a visual preview (thumbnail or first frame), metadata such as tool type or time, and actions. Cards represent batches from AI Tools (image sets, detail pages, viral video, clone video) and completed skill runs from AI Assistant.
Use preview to reject obvious misses before you download—wrong aspect ratio, unreadable label, or off-language copy should trigger a brief fix in the source tool and a new Generate, not manual patching of every asset if settings were wrong.
Preview before download
Click a card to open detail when the UI offers an expanded preview—especially important for video runs where motion and pacing matter. For image sets, scan all frames in the batch; marketplace carousels often need both a clean hero and a readable USP slide.
If preview is slow, wait for processing to finish on the server side. Runs started but not completed may not appear or may show incomplete states—retry refresh after a minute rather than duplicating an in-flight job.
Download assets
Use Download on the card or inside the detail view. Save files with a naming scheme that includes SKU, tool, and date so later uploads to ad managers stay traceable.
Download immediately after approval if your workflow allows—treat History as the primary retrieval path, not a long-term DAM. Team policies may still require copying files to shared storage after download.
Empty History scenarios
- Brand-new account — Empty state is normal until your first successful generation completes.
- Wrong account — You generated while signed into another email; sign out and use the account that pressed Generate.
- Run still processing — Wait and refresh; do not assume failure until an error message appears on the tool page.
- Run failed before save — Failed jobs may never appear; fix inputs on the tool and regenerate.
Workflow tips for teams
Align one Rhinobird login per client or brand when you need clean History separation. Before client review meetings, filter mentally by recency—open the latest image set and viral video entries from the same product photo batch for consistent storytelling.
When a teammate asks “where is the ad?”, send them to History on the shared account rather than re-exporting from local Downloads folders with ambiguous names.
After download on ad platforms
After download, upload to your ad platform or PIM. If platform rejection happens (aspect ratio, file size), adjust settings on the originating tool—Image Aspect Ratio or video Aspect Ratio—and generate a replacement batch; then fetch the new files from History using the same preview-and-download flow.
Quick checklist
- Sign in with the same account used for Generate.
- Open History from the sidebar.
- Preview the run; confirm product identity and copy.
- Press Download and archive with a clear filename.
- Regenerate from the tool only when preview shows a settings or brief issue—not when download simply was forgotten.