Back to the journal

Reve Generation Has Ended. Your Export Job Hasn’t.

Reve users can download generated assets until 31 October 2026, but references are excluded. Here is how sellers can preserve a reproducible product-image workflow.

Reve’s image and video generator stopped accepting new work on 27 September 2026. The urgent task for existing users is now recovery: Reve says account holders can download their generated assets until 31 October 2026.

For a product seller, downloading the final JPEGs is not enough. A usable image workflow also depends on the original product photographs, reference images, prompts, decisions and SKU context that produced those files. Reve’s official export instructions say uploaded images and references are not included in the generated-assets download. If those inputs exist only inside the service, the exported results may be much harder to recreate or revise later.

Start the official export now

Sign in to the Reve web app and use the download banner to prepare an export. Reve says the web export can include generated images and videos from both the web and mobile apps. You can request everything or select a date range.

Do not leave this until the final day. Large libraries can take time to package. Reve also says prepared download links expire after two days and that a new download can be prepared only once every 24 hours. Starting early gives you time to discover a missing date range, an expired link or an incomplete archive and request another package.

After downloading, open every ZIP rather than treating the completed transfer as proof that the archive is sound. Compare the file count with the library, spot-check old and recent projects, and keep at least two copies in locations you control.

Save the inputs the export leaves behind

Reve’s generated-assets export does not include uploaded images or references. Those files often carry more commercial value than a large folder of experiments because they establish what the real product looks like.

Manually recover the original packshot, additional angles, logo files, style references, colour palettes and any image used as a literal product reference. If an input is already stored elsewhere, confirm that the archived version is the same file used in the project. A resized screenshot or an older packaging design may not be an adequate substitute.

Prompts and working instructions also need attention. Copy the final prompt, useful intermediate prompts and any custom instructions that materially changed the result. Record whether an attachment was meant to be interpreted literally or used only as inspiration. Save enough context that another person could understand which image defined the product, which defined the scene and which supplied only mood or lighting.

If the interface does not offer a clean export for those details, use a simple text document or spreadsheet. Screenshots can preserve context, but searchable text is easier to reuse.

Turn a folder of files into a product archive

Bulk exports usually preserve assets, not business meaning. Rename or index the important files while the project is still familiar. At minimum, connect each approved image to its SKU, product name, colour or material variant, channel, aspect ratio and approval status.

A practical filename might contain the SKU, view, campaign and version. The exact format matters less than consistency. Separate approved product-page images from experiments and rejected generations so a plausible but inaccurate image cannot drift back into a future listing.

For jewellery, add the details that determine whether a generated image represents the item accurately: stone count, setting, engraving, chain, clasp, metal colour and intended scale. For packaged goods, note the approved label version and any text that must remain readable. Keep the real product photographs as the reference masters, even if a generated image was the final marketing asset.

Recover the approval trail

A generation history can contain useful evidence about what failed. Preserve notes for images rejected because the logo changed, a clasp disappeared, a colour shifted or the model invented an accessory. Those failures become test cases for the next tool.

Create a small migration set rather than feeding an entire catalogue into a replacement immediately. Choose five to ten difficult products that expose different risks: reflective metal, fine chain links, dense label text, translucent material, repeated pattern or several close colour variants. Rebuild one familiar scene for each product and compare the result with the archived reference at high zoom.

Judge the replacement on product accuracy before visual appeal. Check geometry, countable details, text, colour, scale, shadows and edge quality. Record the prompt, reference set, model or mode, output settings and pass-or-fail result. A tool that produces a beautiful first image but cannot repeat an approved SKU reliably may cost more review time than it saves.

Do not replace one dependency with another

Reve’s closure is a useful reminder that a generation library is not an asset-management system. A seller should be able to change tools without losing product truth or production history.

Keep an independent master folder for original photographs, references, prompts, approved outputs and a compact manifest that explains each file. Store it in a backed-up location controlled by the business. If a workflow is important enough to support product pages, ads or seasonal campaigns, document it outside the tool that performs the generation.

When evaluating a replacement, ask what can be exported, whether uploaded references are included, how long deleted or cancelled accounts remain accessible, and whether prompts and project metadata can be recovered. Also test the capabilities that mattered in the old workflow, such as precise editing, text rendering, high-resolution output, multi-reference control and repeatability across variants. Marketing demos are not a substitute for testing your own difficult SKUs.

The deadline is the useful part of this news

There is no need to rush into a new platform before the archive is safe. The immediate sequence is simpler: download all generated assets, manually collect excluded references, save the instructions that made approved images reproducible, then organise the result around products rather than around a discontinued app.

Reve’s published deadline is 31 October 2026. Finishing the archive well before that date leaves room for a second export and a proper integrity check. The goal is not merely to keep the pictures. It is to keep enough evidence to make, assess and update them somewhere else.

Sources

Reve Help Centre: Downloading Your Reve Assets: https://help.reve.com/hc/en-us/articles/53569023228180-Downloading-Your-Reve-Assets

Reve Help Centre: Attachments: https://help.reve.com/hc/en-us/articles/46796777349652-Attachments

Reve Help Centre: Manage Your Content: https://help.reve.com/hc/en-us/articles/46809623175316-Manage-your-content

Reve AIAI product photographyproduct image workflowdigital asset management