Archive an authorized Framer site as portable files with version history, so a redesign, an expired plan, or a mistake never means losing the page.
A backup you can actually restore
A screenshot is not a backup. LayerPort captures the working pages and assets, so a backup is something you can preview, edit, and republish -- not just look at.
Versioned, not overwritten
Each capture is kept with atomic version history. Compare states, restore an earlier one, and keep a record of how the site changed over time.
Off-platform and portable
Backups live as files you hold, independent of any single hosting account. Export a ZIP for cold storage or push a copy to a second host.
What each kind of backup actually preserves
A backup is only a backup if it restores without the thing that made it. Three of these do not.
Method
Restores without the platform
Keeps assets
Editable afterwards
A Framer project duplicate
No — it needs Framer
Yes
Yes, in Framer
Screenshots or a PDF
Yes
No
No
Save page as
Partly
Some — the ones that loaded
Barely
A localized capture
Yes
Yes, every variant
Yes, visually and as files
What a backup has to contain to be worth having
Every route, not only the pages linked from the navigation
Every image variant, every font file, every stylesheet, localized
A date, so you know which version of the site you are holding
A README that lets someone else restore it without asking you
A test: serve the folder offline and walk it before you file it away
Working pages and assets, not screenshots
Atomic version history and restores
Portable ZIP you keep off-platform
Republish a backup at any time
For sites you own or manage
FAQ
Is a backup just an image of the page?
No. It is the real captured site -- files you can restore, edit, and republish.
Can I keep multiple versions?
Yes. Every capture is versioned, so you can compare and restore earlier states.