Yes, but Duda's own export runs only inside the Duda account that holds the site. Duda's Site Export, on the Agency plan and higher, downloads a ZIP of the published site's HTML, CSS, JavaScript and media; the store, blog pages, dynamic pages, member data and working forms stay behind. If an agency built your site, only its owner or staff can run that export and Duda support won't hand the site to you, so your routes are the agency's export and CSV files, copying the live pages into static HTML files, or a rebuild.
The account holder decides what leaves
Duda's pricing FAQ describes the platform as built for businesses offering websites to other businesses. An agency buys the account, builds client sites inside it and decides what each client can touch. White Label and Custom plans can put the agency's brand on the dashboard and platform emails, and Duda tells agencies their clients won't know they use Duda unless told.
Check whether your site is on Duda
Duda's go-live instructions point the www record at s.multiscreensite.com and the root domain at two IP addresses. Look both up from any terminal:
nslookup www.yourdomain.com
nslookup yourdomain.com
If the first answer names s.multiscreensite.com, or the second returns 35.172.94.1 and 100.24.208.97, Duda is serving the site. A different answer doesn't rule Duda out, since Custom plans on Duda's EU instance use other records. A site without a custom domain lives at a sitename.dudasites.com or sitename.multiscreensite.com address, or on a White Label agency's own subdomain.
What a client login can and can't do
Agencies create client logins and grant permissions one site at a time (Manage Clients), and they can suspend that access. Whatever permissions you hold, Duda's Site Export article restricts exporting to the account owner and staff member roles. A client is neither.
Ownership is murkier. Duda's Terms of Service, updated September 2026, say Duda doesn't own or claim the content on sites, but that clause is between Duda and its customer, the account holder. Whether the copy, photos and design are yours or the agency's depends on your contract with them. Duda says it won't act as an intermediary or arbiter in transfers, and it disclaims liability for disputes between account owners and clients "that may own Sites built through the Platform." Its transfer article is blunter: Duda support does not transfer sites, and a client who needs ownership has to go to the site's account owner.
Moving the site into your own Duda account
To stay on Duda, ask the agency to transfer the site. The receiving account needs an active subscription, and the transfer link expires after 24 hours. Once it moves, the site's subscription is canceled and the site stays unpublished until you buy a new one. Sites with paid add-ons, Site-for-Life status, Client Billing or an unpaid invoice can't be transferred. Contact form responses might not come along, and a store's plan is canceled, though order history stays.
What Duda's Site Export contains
Open More > Settings > Site Export and click Export Site. Duda's rules, as of its October 21, 2026 update:
- Plan: Agency or higher. The pricing page ticks "Code export" for Agency, White Label and Custom only. As of October 2026, Agency costs $52 a month billed annually or $69 billed monthly.
- Live version only: the site must be published, the ZIP holds what's live rather than editor drafts, and the limit is 1 GB.
- Three copies: Duda serves content by device, so the ZIP has one folder of HTML and CSS each for desktop, tablet and mobile. Only images used on the desktop site are exported.
- One way: the ZIP can't be imported into another Duda account, and Site Export isn't available for Duda Vibe projects.
Left out of the ZIP: the store (products export separately as CSV), the blog (only in the .rss file), dynamic pages, the 404 page, password protection (the pages come, the protection doesn't), personalization triggers, and membership and app data. MapBox maps switch to OpenStreetMap. The OpenTable widget, the Share widget's email option, the vcita scheduling button and Instagram-connected product galleries appear but don't work. Contact forms stop working and Duda's visitor stats end, though Google Analytics stays.
You also may not unminify the exported JavaScript and CSS, or copy Duda's template designs to sell. The pricing page's tooltip states the catch: server-side code isn't included, so the files may not behave as the site did on Duda.
In practice, a 2023 Netlify forum thread shows an export with pages under Pages/desktop, Pages/mobile and Pages/tablet and the home page in a home folder. A helper got it loading by copying the desktop folder to the root and moving the home page to /index.html, warning that some things were still broken and every change would need redoing after each new export.
Everything else, one export at a time
Beyond the ZIP, each kind of data has its own export, all in Duda's help center as of October 2026.
| Data | Where Duda exports it | Left behind |
|---|---|---|
| Published pages | Site Export ZIP, Agency plan or higher | Store, blog pages, dynamic pages, forms, members |
| Blog posts | Copy the RSS feed URL from Blog Settings and save the XML (Blog) | Images stay on Duda's servers as links |
| Internal collections | CMS > Collections > "..." > Export to CSV (Internal Collections) | The dynamic page templates built on them |
| Native store products | Store > Catalog > Product Catalog > Export (products) | Checkout and payment setup |
| Native store orders | Store > Sales > Orders > Export (orders) | Order management |
| Third-party store | Products, orders and customers to CSV, Advanced Store plan and higher (export) | The store itself |
| Form submissions | Site Dashboard > Form Responses > Export to CSV (Contact Forms) | The forms; uploaded files expire after 90 days |
| Members | More > Membership > Site Members > Export to CSV (Membership) | Logins and members-only pages |
| Booked appointments | Bookings > Booked Appointments > Export (Manage Bookings) | The booking system |
Google Sheets and Airtable collections already live in those tools. Duda's native store articles document no separate customer export, but its order CSV carries each buyer's email, billing and shipping details. Duda calls the members file a list of members and doesn't mention passwords, so expect members to set new ones. Duda's backups are restore points inside the editor, not downloads.
Blog feeds can be complete: Duda's own, at duda.co/feed/rss2, held 641 posts back to 2013, each with its full HTML, when we downloaded it on October 24, 2026. Its images pointed at irp.cdn-website.com, where Duda hosts editor uploads, so save the image files too.
If the agency is slow, ask for the eCommerce and Content Library client permissions, which cover the catalog, orders and collections and may let you run those exports yourself.
The domain is a separate question
Duda says its site builder does not host domains. Domains reach Duda through DNS records, so leaving means changing them at the registrar:
- Bought in Duda's publishing flow: it's registered with IONOS, which Duda names as your point of contact. Basic, Team, Agency and White Label include the first year free, up to $12 in value.
- Bought through Duda on a Custom plan: only the account owner, or a client the owner has given permission, can change or remove one (Purchase Site Domain).
- Bought at a registrar: it stays there. Find which one at lookup.icann.org.
If the agency registered the domain under its own name, ask it to make you the registrant, or for the transfer code. For .com and other generic domains, ICANN's registrant FAQ says a registrar must provide that code within five calendar days. Changing the registrant's name, organization or email triggers a 60-day lock on changing registrars, so ICANN suggests transferring first.
Three routes off Duda
1. The native export
Best when the agency's account already has it and you have a developer, or when you want an archive of exactly what was live. Expect cleanup: choosing a device folder, fixing paths, replacing what's missing.
2. Copy the live site into static HTML
This copies what a visitor's browser receives. It needs no Duda login, plan upgrade or agency cooperation, and it picks up rendered blog posts and dynamic-page records when it can reach them, both of which the native export leaves out. Duda's sitemap lists blog posts, dynamic page records, and store category and product URLs, so use it as your checklist, plus any pages set to noindex, which it leaves out.
Anything that needs Duda's servers can't come: form submissions, cart and checkout, bookings, member login and members-only pages, password-protected pages, personalization, Duda's stats, and the collection behind dynamic pages. Captured record pages are fixed copies, and a new record won't create a page. Duda serves content by device, so check the result at phone width too. Two more limits:
- Duda may block it. Duda's traffic article says its security systems can block third-party crawlers with a 403 error. Editing robots.txt doesn't help, and there's no setting to allow an IP address; support can review a tool on request without promising to allow it.
- The site has to be online. With auto-renew off, a site unpublishes at the end of its billing cycle, and deleted sites can be restored only within 30 days (subscriptions). Capture before the agency winds the account down.
FNJ's Duda to HTML converter takes the site's public URL and saves its pages as static HTML. From there you keep the files locally, send them to a GitHub repository of yours, or publish them on a Cloudflare Pages or Vercel account you own, using your own token. FNJ doesn't host the site. Forms, stores, bookings, member areas and the CMS backend aren't exported and need replacement services, and if Duda blocks the capture, FNJ reports it rather than produce a broken export. Before switching, work through the Duda export guide. Converting requires a paid FNJ plan (pricing).
3. Rebuild
Rebuild when the store, bookings or member area is the business, or when you want an editor again. The CSV files feed the new platform's importers, and a capture or the ZIP serves as the visual reference.
Keep your URLs working
Save yourdomain.com/sitemap.xml before anything changes. Only published Duda sites have one.
Duda's URL Redirect rules only cover paths on the domain assigned to the Duda site. After the domain moves, rebuild every redirect on the new host. Duda addresses carry no file extension (/about, not /about.html). If you host the export, copy (don't move) the desktop pages to the root, because serving them from /Pages/desktop/ changes every address; in the 2023 thread, pages still loaded styles from the originals.
On Cloudflare Pages, redirects go in a _redirects file in the root of the folder you deploy. Its docs set 302 as the default status, so write 301, and one file holds up to 2,000 static and 100 dynamic rules. Example paths only, old path first:
/services-1 /services 301
/meet-the-team /about/team 301
/blog/* /articles/:splat 301
Google recommends a permanent server-side redirect (301 or 308) when a URL changes, and its site move guide advises leaving them in place, generally for at least a year. For building the old-to-new list and testing it, see the redirect map guide.
What to ask the agency for
- The name of the Duda account owner and the domain's registrar.
- A transfer to your Duda account, or the Site Export ZIP.
- CSV exports of form responses, products, orders, collections, members and bookings.
- Copies of sitemap.xml and the blog's RSS feed.
- The domain's transfer code, or a change of registrant to you.
- A promise to keep the site published until your new site and its redirects are live.
Frequently asked questions
How do I download a Duda website as HTML?
Use Site Export, which needs the site's account on the Agency plan or higher and you as its owner or a staff member. It downloads a ZIP of the live site, up to 1 GB, with desktop, tablet and mobile folders, but without the store, blog pages, dynamic pages or working forms. Without that access, copy the public pages instead, unless Duda blocks it.
Which Duda plans include site export?
Agency, White Label and Custom; Duda's pricing page doesn't list code export on Basic or Team. As of October 2026, Agency costs $52 a month billed annually or $69 billed monthly, and White Label $149 or $199.
My agency built my site on Duda. Can I take it with me?
The Duda site itself, only through the agency. Duda support doesn't transfer sites and sends clients to the account owner, and client logins can't run Site Export. Ask the agency for a transfer to your own Duda account, or for the ZIP, the CSV exports and the domain. Whether you own the content depends on your contract with the agency.
Can I export my Duda blog posts?
Duda's documented method is the blog's RSS feed: copy its URL from Blog Settings and save the XML from your browser. The Site Export doesn't include blog pages in its HTML. Images in the feed point to Duda-hosted files, so download them separately.
Does a Duda export include the online store?
No. Native store products export to CSV from the Product Catalog, and orders export with items, totals, buyer emails, addresses and payment status. The third-party store, found only on Classic Editor sites, exports products, orders and customers on Advanced Store plans and higher. Checkout and payments have to be set up again.
Do I keep my domain if I leave Duda?
Yes, if you control its registration. Duda doesn't host domains; a domain points at Duda through DNS records. One bought in Duda's publishing flow is registered with IONOS, and one bought elsewhere stays with that registrar, so point its records at the new host or move it with the transfer code.
Starting a new site instead? FNJ's AI website builder designs one from a description and a site you like, then gives you the code to host anywhere.
