NanoMaker Files Vanish After Fourteen Days Unless Downloaded

News desks lose AI graphics in a way that looks like forgetfulness and is actually a product clock. A thumbnail still sits in a browser tab while the file behind it has expired. Treat NanoMaker like infinite storage and that clock will punish you on publish day — not because editors forgot the story, but because the workspace was never a DAM.

Public docs are blunt: generated images, videos, music, and audio — including Public outputs on Explore — expire after 14 days, and the browser keeps only the most recent 16 generation records locally. For a Panama English newsroom shipping daily explainers, that sentence is the thesis. Everything else waits until archive hygiene is boring.

The Publish Hole Starts as a Thumbnail That Lies

Homepage slots do not care that a preview looked fine last week. Layout asks for a path. Slack holds a thumbnail. The generator returns an expired object. On the newsroom desk, producers usually discover the miss when the caption is already approved and the same-day window is half gone. Someone regenerates from memory, burns credits, and still misses the crop the caption described. That single discard of the dead tab is a hard fail for publish even when the new draft “looks fine.”

Readers never hear the argument. They only see a late chart or a recycled stock stand-in. The cost is reporting time converted into re-work — an afternoon that should have been phone calls, not prompt archaeology. Editors feel the miss as embarrassment; reporters feel it as a story that lost its visual proof at the worst hour.

That is why expiry belongs in the morning meeting, not in a forgotten FAQ bookmark. If producers cannot name where keepers live, the generator is still being treated as a filing cabinet. Ask the question out loud once a week until the answer is boring: “Where does today’s approved chart live outside the tab?”

Fourteen Days Is a Staffing Fact, Not a Footnote

Put the published clock against real packages. A feature drafted early in the month can sit in review while the asset ages out. A weekend explainers queue can outlive Friday’s generation. Election or summit weeks stretch further when legal holds a portrait for one extra check. Sixteen local records sound helpful until the seventeenth take of the week pushes the keeper you meant to reopen out of quick reach.

Desk situation	What the clock does	Publish risk
Asset left only in workspace	Can expire before layout	Homepage hole
Rely on local recent list	Only last 16 stay handy	Older keepers hard to reopen
Regenerate under deadline	Credits burn; crop drifts	Caption no longer matches art

If your CMS already owns the canonical file, the AI tab can stay disposable. If layout is still pointing at the AI tab, you have inverted the archive. NanoMaker AI did not create that inversion; desk habit did. The expiry rule only makes the habit expensive.

Name an owner for download on every graphic assignment the way you name a reporter. When “someone” owns it, nobody does. When a producer owns it, fourteen days becomes a calendar reminder instead of a surprise. That staffing detail matters more than another model comparison thread in the newsroom Slack. Tools do not archive themselves; people with clear names on the assignment do.

Three Old Fixes That Feel Cheap and Are Not

Regenerate the “same” prompt under deadline. Identity drifts, numerals move, and the caption written against version one no longer matches version four. Screenshot the browser preview. Print partners reject the mush. Paste generator links into Slack threads. Links are not files after the object dies.

Each path wastes an afternoon that should have been reporting. In our desk pipeline, a graphic that is not in the CMS by shift end counts as unpublished even if a preview still flickers in a tab. That rule sounds harsh until you watch a homepage hole open because nobody owned the download. When legal locked a portrait for an extra day last cycle, the desk with a CMS working copy simply swapped the final; the desk that left the only copy in the generator lost the slot and apologized to the reporter. Same tool both days. Different archive habit. Only one desk still had a publishable file.

Make the Generator Disposable With One Archive Rule

Use a Nanobanana maker style run only after the story desk names the destination slot. Accept the frame after caption and phone-width crop agree — unreadable axes are a soft fail for social and a hard fail for print. Download that keeper, rename with story slug and date, and attach it to the CMS package before the shift ends. Keep prompt text beside the file when legal might demand a rebuild; the prompt is insurance, the download is the archive.

Scratch Pad Versus Keeper Files on Disk

The recent sixteen generations are a same-sitting scratch pad. They are not a month-long library. Morning meetings should say that out loud: scratch stays in the tool; keepers leave the same hour. Producers who need more history than sixteen entries already waited too long to download.

Credits Matter Only After Folders Exist

Free signup credit (6 on first sign-in) proves a chart style; it does not staff a week. Paid yearly tiers advertise unused-credit rollover and commercial-use language — useful for sponsored packages — but rollover never revives an expired file. Credits buy new generations. They do not unlock deleted history. Route cheap drafts for charts and save heavier lanes for covers only after the download rule is non-negotiable. A morning spend of a few cheap drafts is fine; a morning spent rebuilding an expired keeper is not a model problem.

Where the Expiry Rule Still Needs Human Judgment

The 14-day limit does not invent editorial taste. Long investigations, embargoed packages, and legal-held portraits still need a human to decide when a file is done enough to download. If that decision cannot land inside two weeks, park a working copy in the CMS draft folder early, then replace it when final approval arrives. Judgment stays human; the clock only punishes delay. NanoMaker AI remains useful inside that judgment — it simply refuses to be the long-term shelf.

Shift Close Means Keepers Live Outside the Tab

For English-language desks in Panama and similar fast markets, win with a dull checklist: accepted frames downloaded, renamed, attached to the story package. NanoMaker AI can remain the birthplace of the graphic. It should never be the only home when the homepage is counting on the file. If you already auto-ingest downloads into a real DAM, you will feel little pain. If layout still opens a browser tab for the master, fix that before debating another plan tier.

The tool can stay. The illusion that the tool is the archive cannot. Once that sentence is shared without apology, fourteen days stops being a scare story and becomes a simple staffing constraint — the kind newsrooms already know how to manage when the constraint is named out loud. Name it, assign it, download it the same hour. Then go back to reporting.