Generation is only useful when you can preview truthfully and download files that pass channel QA. Rhinobird stores completed runs in History with previews and Download actions. When preview spins, files save corrupted locally, or images look soft at full zoom, work through retrieval first, then source quality, then regeneration. This article covers download and preview failures plus low-clarity output on the English UI.
Standard preview and download flow
- Sign in with the account that pressed Generate.
- Open History from the sidebar or the generation history route.
- Click the run card; play video previews fully or scan every image in a set.
- Press Download on the card or inside detail view.
- Archive with a filename that includes SKU, tool, and date for your team.
Download soon after approval when your workflow allows. History is the primary retrieval path; local folders should be a copy, not the only copy.
When preview will not load
Previews depend on processing finishing and your session staying valid. If preview hangs:
- Refresh History once; wait if the job may still be processing on the server.
- Re-authenticate via Login / Sign up if the tab sat idle for hours.
- Try another browser to rule out extension interference.
- Return to the originating tool only if History shows failed or missing delivery.
Do not download blindly when preview fails—you may grab an incomplete file or an older cached asset from your operating system.
When download fails or saves empty files
Retry Download once from History detail view. Check browser download permissions and corporate policies that strip attachments. Disable “ask where to save” temporarily to see if dialogs are blocking silently. If multiple formats are offered, pick the default export the tool documents. Still failing? Note run time and account email, then contact 13378452864 or support@rhinobird.ai with browser version and screenshot.
Fix low clarity before and after generation
Blur often starts with weak uploads. Before Generate, ensure product photos meet JPG or PNG limits and show readable labels. Use AI matting to isolate the product and AI upscale when resolution is below your marketplace standard. After generation, stills can sometimes be improved by upscaling the exported PNG or JPG—within tool limits—before manual retouch. Video blur usually requires regeneration with sharper sources and shorter proof durations, not single-frame upscale alone.
Regenerate when clarity fails QA
If full-size download fails label readability tests, tighten Creative Requirements to demand legible packaging text, replace the hero photo, and run a low-cost proof. Compare new and old entries in History before deleting anything your legal team might need. Re-read credit cost on Generate; fixing clarity is intentional spend, not a hidden refund scenario unless the job truly failed to deliver.
Credits and failed delivery
When there is no deliverable because of system error, timeout, or cancellation before execution, membership rules may return pre-deducted credits—verify credit transaction details. When a file downloads but looks unusably soft, treat it as creative iteration unless support confirms a platform defect. Disputes follow pathways described in Service Agreement.
Team handoff tips
Share History access on the shared account rather than forwarding mystery attachments. Tell reviewers to zoom product labels to one hundred percent before approving. Pair download with your DAM or ad manager upload checklist so low-clarity files never reach live campaigns.
Preview honestly, download once you trust the asset, and fix clarity at the source photo when possible. History plus matting and upscale prep prevents most “unusable file” surprises.