How to export your data from Netlify
Netlify has no single 'export all data' button. You download each site's built output as a ZIP from the Deploy file explorer, and you download Netlify Blobs data (if you used that feature) one blob at a time from the Blobs UI or via the CLI; your actual pre-build source code lives in your connected Git repo, not on Netlify.
✓ Verified against Netlify's official documentation, September 2026
Step by step
- 1Log in to the Netlify Admin UI at app.netlify.com and open the site you want to export.
- 2Go to the site's Deploys page and select any successful deploy (production, branch, or preview).
- 3In the deploy detail view, above the Deploy log panel, use the download link in the deploy summary to get the entire deploy as a single ZIP file containing all deployed assets.
- 4Optionally, use the Deploy file explorer below the Deploy log to browse the build's asset tree and inspect or download individual files instead of the whole ZIP.
- 5If the site uses Netlify Blobs for app data, go to the project's Data & Storage > Blobs page, select the store, drill into directories, and download blobs individually — or script bulk retrieval with the Netlify CLI.
- 6Pull or clone your connected Git repository (GitHub, GitLab, or Bitbucket) separately — the deploy ZIP only contains built output, not your original editable source files.
- 7Manually note site configuration (build settings, redirects, headers, environment variables) from Project configuration in the Netlify UI, since there is no documented one-click export for these settings.
What the export includes
- ✓The built/deployed site files (HTML, CSS, JS, static assets) for the specific deploy you download
- ✓Netlify Blobs data, downloaded blob by blob or store by store
- ✓The full asset tree of any successful deploy, browsable in the Deploy file explorer
What it doesn't include
- ✗Pre-build source code — only available from your connected Git repository, not from Netlify itself
- ✗Environment variables — must be copied manually, no documented bulk export
- ✗DNS records, domain configuration, and team/collaborator membership and roles
- ✗Anything not part of a completed, successful deploy
Before you start
- ⚠There is no account-wide or team-wide export — everything is downloaded per site and, for Blobs, per store
- ⚠The deploy ZIP reflects only that specific deploy's build output, not your working source tree
- ⚠Blobs are downloaded one at a time through the UI unless you script bulk downloads with the CLI
- ⚠You must pick a specific successful deploy in the Deploys list before the file explorer or ZIP download becomes available
Where to take your data
Free and cheaper tools that can take a Netlify export. See all Netlify alternatives →
Cloudflare Pages
Connect the same Git repository to Cloudflare Pages and let it rebuild from source; use the downloaded deploy ZIP only as a static fallback if the repo isn't available.
ArLink (Arweave)
Take the built files from your downloaded deploy ZIP (or the Deploy file explorer) and drag-and-drop that output folder into ArLink to publish it permanently on Arweave.
Netlify Free
If the goal is just cutting cost rather than leaving, downgrade the same team to the Free plan — your existing deploys and blobs stay in place with no migration needed.
Exporting from Netlify: common questions
Can I export my whole Netlify site in one click?+
You can download a full deploy as a single ZIP file from the deploy summary panel on the Deploys page, but this covers one deploy of one site at a time, not your whole account.
Does the exported ZIP include my original source code?+
No. It contains the built output (HTML/CSS/JS/assets) generated by that deploy. Your editable source lives in your connected Git repository, which you should clone separately.
How do I get data out of Netlify Blobs?+
Open Data & Storage > Blobs for the project, pick a store, and download blobs individually through the UI, or use the Netlify CLI to retrieve them programmatically.
Do I need a paid plan to download deploy files or blobs?+
No plan restriction is documented for the Deploy file explorer or the Blobs UI — both are accessible from the standard Netlify Admin interface.
Can I download an old deploy, not just the current production one?+
Yes. Any successful deploy listed on the Deploys page — production, branch, or preview — can be opened individually to view its file explorer and download its ZIP.
What about environment variables and site settings?+
There's no documented bulk export for these. Copy them manually from Project configuration in the Netlify UI before migrating or shutting down a site.
Sources
This guide was written from Netlify's own documentation and checked against it in September 2026. If a step has changed, the official page wins.
Netlify head-to-head
More Dev Tools tools people are leaving
All Dev Tools alternatives →What would you save without Netlify?
Pick your team size and see the yearly number.