Two things happened in the last fortnight: OpenAI's Sora API reached its final weeks with no documented answer about stored content, and Miro agreed to be acquired by a company with a documented history of restricting free tiers. Neither is a crisis. Both are the same reminder, which is that the question to ask about a creative tool is not what it makes but what you get out, and almost nobody asks it before adopting.
The one habit that matters
Export at the end of every project, not at the end of a tool.
Everything else on this page is detail. A twenty-minute pass when a project closes (finals, sources, and the working files, into storage you control) means no shutdown, acquisition, or price change is ever an emergency. Teams that do this treat vendor news as a procurement question. Teams that do not treat it as a fire drill, twelve days out, which is where Sora users are this week.
What to export, in priority order
1. Finals. The assets that shipped. Obvious, and still the thing people assume is safe because it is "in the tool."
2. Sources. Original capture, uploaded reference images, the raw files everything derived from. Irreplaceable in a way finals are not.
3. Prompts and reference sets, for generated work. This is the one people miss. For a generated asset, the prompt plus the reference images is the source file, in the same way a RAW file is for a photograph. Export the outputs without them and you have pictures you can never make another version of. See how to organize creative assets.
4. Model and settings. Which model, what duration, what resolution. Matching an old asset later is impossible without them.
5. The decisions. Briefs, approved boards, feedback threads. Worth less individually and it is the institutional memory that makes the next project faster.
Which formats survive
Safe: JPEG, PNG, MP4, WAV, PDF, plain text, CSV. Boring formats outlive the companies that wrote them.
Conditionally safe: layered files and project files, which open only in the software that made them. Fine as an archive, useless if that software is what went away.
Not safe: anything that exists only as a link into someone's platform. A board you can only view by logging in is not an archive, and neither is a share URL.
The test: if the company vanished overnight, could you still open this in five years? If the answer needs their servers, it is not archived.
The questions to ask before adopting
Ask them at evaluation, when the vendor is motivated to answer:
Can I export everything, in bulk, in standard formats? Not one file at a time. Bulk.
What happens to my content if I stop paying? Read-only, deleted, or held hostage behind a reactivation fee. All three exist.
Is there a documented data-retention policy? The Sora situation is instructive precisely because the answer to "what happens to my generated content" was never published, and six months of deprecation notice did not produce it.
Who owns the output, and does that survive account closure?
What is the notice period for a material change?
A vendor who answers these crisply is telling you something real about how they operate. A vendor who cannot is telling you something too.
Our own answer, since we are asking
It would be dishonest to publish this checklist without applying it to ourselves.
Per-asset download: yes. Every generated and uploaded file can be downloaded individually in standard formats.
Bulk board export: no, we do not have it. You cannot currently export a whole canvas in one action. That is a real gap against the checklist above and it is on us to close rather than to phrase around.
Ownership: output from paid plans is cleared for commercial use.
Free canvas: boards and collaboration are free and unlimited with no expiry, and AI generation is the paid layer from $19/month.
If bulk export matters to your procurement decision today, that is a legitimate reason to weigh us down, and we would rather you knew before adopting than after.
What not to do
Do not panic-migrate on an announcement. Miro has announced no product changes and the deal has not closed. Moving a working team in a week costs more than any plausible price rise. See Miro acquired by Bending Spoons.
Do not assume "the files are in the cloud" is a backup. It is someone else's computer, under terms they can change.
Do not archive only the finals. Prompts and sources are what let you make version two.
FAQ
How often should we export? At project close, every time. Continuous backup of working files is overkill; an archive pass at the end is not.
What if a tool has no bulk export? Factor it into the decision, and export per project so the manual cost stays small. A tool without bulk export is not disqualified, it is a known cost.
Is a screenshot of a board an archive? It preserves the arrangement and nothing you can edit. Better than nothing for reference boards, useless for working files.
The question is never what a tool generates. It is what you carry out when you leave. The 8frame canvas is free and unlimited, and generation is paid from $19/month.