No. Strikingly has no site export or HTML download on any plan, from Free to VIP, and its help center tells people who leave that they will have to rebuild elsewhere. What can come out is data: products, orders, form responses, users and booking records as CSV files, plus any domain you registered through Strikingly. For the pages themselves, the options are a static HTML capture of the live site or a rebuild.
What Strikingly's help center says
Four help articles cover the question, all checked in October 2026:
- Leaving Strikingly / Export Site: exporting sites isn't allowed yet, and anyone changing platforms has to rebuild.
- Can I download my website?: no, because the site editor has to stay connected to Strikingly's servers. Offline editing isn't possible either.
- Can I get a copy of my website's HTML file?: no direct access to your HTML.
- Print Site as PDF: screenshot each live page, for example with the GoFullPage extension, and warns that browser printing may come out poorly.
The pricing page agrees: no plan lists an export. Pro and VIP include Site History, but it restores an earlier published version inside Strikingly and can't bring back blog posts, store categories or coupons. It's an undo, not a backup you hold.
The demand is old. An "Export as HTML" request has sat in Strikingly's Idea Forum since June 2015. Strikingly's only official reply, that December, promised to be in touch once it worked on the feature. In October 2026 the post had a net score of 10 from 16 votes, and no status.
One clause in the Terms of Service sets the order of your move. Strikingly doesn't claim ownership of your content, but once you cancel the service you lose access to the website and Strikingly may delete everything on it. Canceling just a paid plan is milder, since you drop to Free and keep the editor. Either way, take every export below first.
What you can export, item by item
Every row is taken from Strikingly's help articles, read in October 2026.
| Item | Where to export it | Left behind |
|---|---|---|
| Pages and design | No export | Everything; capture or rebuild |
| Blog posts | No export. "Copy to" in the Blog Posts Manager only sends posts to another Strikingly site | Post text, images and comments |
| Store products | Store > Products > More Actions > Export Products, then Download | Digital products, which can't be exported |
| Orders | Store > Orders > Export Orders; the CSV downloads straight away | Checkout, payments and refunds |
| Form responses | Users > Forms tab > More Option > Export Form CSV | The forms themselves |
| Users | Users page > More Options > Export User CSV | Logins, membership tiers, members-only pages |
| Bookings | Editor > Bookings > Scheduled, then download the event CSV | The booking calendar and its emails |
| Domain bought through Strikingly | Repoint its DNS, or transfer it (below) | Email set up on the domain through Strikingly |
| Free mystrikingly.com address | Can't leave; it's Strikingly's subdomain | The address and every link pointing at it |
The users file covers more than its name suggests. Strikingly's Users list collects contact-form and pop-up entries, blog subscribers, booking submissions, store customers, members and live chat visitors, filterable by source, so one export may hold most of the people your site has gathered. Strikingly doesn't document its contents, so check its row count.
Members leave as contacts, not accounts
As of October 2026, membership needs Pro (one tier, up to 100 members) or VIP (five tiers, up to 2,000), per Strikingly's membership article. Members appear in the Users list, so names and emails leave in the user CSV. Nothing documented moves their logins, tiers or access rules.
Paid memberships run only through Stripe, and Strikingly's paid membership article warns that disconnecting Stripe ends every recurring subscription at once. Open the new membership platform first, invite paying members across, and disconnect Stripe last.
Blog posts have no export
The Blog Posts Manager can duplicate a post or copy it to another Strikingly site, and Strikingly documents no file export for its blog. Posts live at /blog/post-title, per the permalink article, so the options are capturing those public pages or copying them by hand. Comments from Strikingly's built-in blog commenting stay behind.
Your domain
Bought elsewhere and connected. A connected domain stays with your registrar and points at Strikingly through two DNS records, per the transfer vs. connect article. Swap them for the records your new host provides; the domain itself doesn't move.
Bought through Strikingly. You keep the rights after you leave, with two options:
- Keep it there and repoint it. The DNS manager accepts A, CNAME, SRV, TXT, MX and NS records, per Strikingly's DNS article. Renewal is billed separately from your site plan, normally $24.95 a year or more depending on the extension (as of October 2026), per the renewal article. Leave auto-renew on; an expired domain takes the site down.
- Transfer it away. Ask support by email or chat to release it. Strikingly then turns off WHOIS privacy, removes the transfer lock and emails the domain's contact address an authorization (EPP) code. The transfer-away article requires 60 days since registration, adds a fresh 60-day lock if you changed contact details, and gives five days to confirm the approval email. Expect one to two weeks, during which DNS records stop working and the site and domain email may go offline.
Move email first. Strikingly's leaving article says addresses set up on the domain stop being valid after a transfer away.
Two money details. If the domain came free with a yearly plan, canceling that plan or switching to monthly in the first year forfeits the offer, per the domain credit terms, which state a US$24.95 domain charge for the switch to monthly. And downgrading to Free disconnects every custom domain, sending each site back to its mystrikingly.com address.
What the free plan's mystrikingly.com address means
A free site lives at an address like yourname.mystrikingly.com, renamable in Settings > Domains, per the free URL article. It's a subdomain of Strikingly's domain, so it stays behind, and every link and search result pointing at it lands on the Strikingly copy for as long as that copy is published.
A free site can't forward visitors. Header and footer code is a Pro and VIP feature, and Strikingly documents no 301 redirect for its own pages. A Pro or VIP owner can add an instant meta refresh to the header code, which sits in the page's <head>. Google treats that as a permanent redirect, though it isn't a 301, and Strikingly strips header and footer code from every site when the plan ends.
That also rules out Google's Change of Address tool, which needs a 301 from the old homepage. What's left:
- Keep the old site as a signpost. Replace its content with a short note linking to the new address. Old links keep working, though nothing tells search engines the site has moved.
- Delete it. Site deletion is permanent, and old links stop working.
Free sites also carry Strikingly's footer branding and an "on Strikingly" suffix on the site title, shown on the browser tab and in search results, per the free site definition. A capture of a free site copies both, so edit them out before launch.
Three routes off Strikingly
| Route | What you end up with | Store, forms, members | Suits |
|---|---|---|---|
| Native export | Nothing. Strikingly suggests a PDF or screenshot per page | None | A record of how the site looked |
| Capture the published pages | HTML, CSS and images of the public pages it finds, blog posts included | Need replacement services | Portfolios, brochure sites, finished blogs |
| Rebuild | A new site on a new platform | Built with the new platform's tools | Stores, membership sites, active blogs |
1. The native route is a PDF
Strikingly's save-as-PDF steps use the browser's print dialog, one page at a time, and may not match the site. It's an archive, not a website.
2. A static HTML copy of the public pages
A capture records each public page as a visitor's browser gets it: markup, styling, copy and pictures. That can include product pages and public blog posts, which none of Strikingly's exports touch, if the capture finds them. It's a snapshot; later Strikingly edits don't follow.
Anything that needs Strikingly's servers stays behind:
- Simple Store: cart, checkout, inventory and orders. Product pages become display pages.
- Forms: contact, sign-up, custom and pop-up forms submit to Strikingly's Users list, so each needs a form service.
- Memberships: the
/i/loginpage and everything behind it. A capture has no login, so it can't reach members-only or password-protected pages. - Other Strikingly services: bookings, live chat, site search and blog commenting. Replace or remove each.
One-page sites need an anchor check. Strikingly links to a section by a slug made from its name in the editor's left panel, such as /#who-are-we, or by position, such as /#2, as its section linking article explains. On Strikingly's own example page, strikingly.com/pro, the section headed "Style your site" answers to #styles-colors, and menu links such as #branding and #styles-colors have no matching id in the HTML the server sends, so Strikingly's scripts must do the scrolling. Click every menu item on the copy and test section links you've shared. Where nothing scrolls, put the id the link expects on the section's empty section-anchor div. Its <li> already has an id, and browsers ignore a second one:
<li class="slide s-section-3 …" id="section-f_…">
<div class="waypoint"></div>
<div class="section-anchor" id="who-are-we"></div>
…
</li>
<!-- a numbered link like /#2 needs id="2" on the anchor div in s-section-2 -->
Multi-page sites are simpler: each page has its own path, such as /about-us, per the multi-page article, and the static copy can use the same paths.
FNJ's Strikingly to HTML converter works from the published site's URL. You can keep the result as files, commit it to your own GitHub repository, or deploy it to your own Vercel or Cloudflare Pages project with a token you create; FNJ never hosts it. Some sites refuse automated capture, and then FNJ stops and tells you instead of delivering a copy with holes in it. The Strikingly export guide covers checking widgets, mobile layout and anchors before the domain moves.
3. Rebuild
Rebuilding is Strikingly's own advice, and the right call for a store or membership site, since those parts need rebuilding anyway. The CSV files carry the data:
- Products: Shopify rejects a CSV whose headers don't match its sample file exactly, so copy Strikingly's data into Shopify's template. WooCommerce's built-in importer lets you map columns by hand.
- Contacts and members: import the user CSV into your email or membership tool, then ask members to sign up again.
- Blog posts: paste them in, or copy text from captured pages.
Keep the paths you can, and give the ones that change server-side 301s at the new host. Google's site move guidance says to keep them for a year or more, and FNJ's redirect map guide helps you draft the list.
A move order that doesn't lose data
- Export products, orders, form responses, users and bookings, and open every file.
- List every public URL, product pages and blog posts included (the site's
/sitemap.xml, if it has one, lists them). - Capture or rebuild, adding replacement forms, checkout and member sign-up.
- Move paying members, then disconnect Stripe from Strikingly.
- Set up email with a new provider, then change the domain's records or move it to a new registrar.
- Add redirects for changed paths and test old URLs on the new host.
- Cancel the plan, then delete any site you aren't keeping as a signpost. Strikingly only deletes a whole account once it's on Free with no sites left.
If your Strikingly site is mostly public pages, FNJ gets them into files you control, and handles that step only; conversions need a paid plan (see pricing). Checkout, logins and forms each need their own new home.
Frequently asked questions
How do I download my Strikingly website?
Strikingly itself won't let you. Its help center rules out downloading a site or its pages, and owners get no access to their HTML files. To get HTML, run a converter or crawler over the live pages; forms, checkout and member logins won't work in the copy.
Does the Strikingly Pro or VIP plan include a site export?
No. Neither plan lists one on Strikingly's pricing page. Both get Site History, which restores an earlier published version inside Strikingly, but it gives you no files and can't recover blog posts.
Can Strikingly blog posts be exported?
There's no blog export. The Blog Posts Manager copies posts only to another Strikingly site. Capture the public post pages at /blog/post-title, or copy each post by hand.
Can I move my Strikingly store to Shopify or WooCommerce?
The catalog can: export products to CSV from Store > Products > More Actions, then import into Shopify after matching its template headers, or into WooCommerce with its column mapping. Digital products aren't in Strikingly's export, and order history comes out as a separate CSV.
Do I keep my Strikingly domain after canceling?
A domain registered elsewhere only needs its DNS records pointed at your new host. One registered through Strikingly stays yours: repoint it in Strikingly's DNS manager and keep paying the yearly renewal, or ask support to release it for transfer, which needs 60 days since registration and takes one to two weeks.
What happens to my mystrikingly.com URL when I leave?
It stays with Strikingly. A free site can't forward visitors, because header and footer code is a Pro and VIP feature, so the choices are a short page linking to the new site or deleting the old one. Without a redirect, nothing tells search engines that the site has moved.
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.
