Is Wix a CMS website?

Yes, with one caveat. Wix is a hosted website builder that includes a CMS, so a Wix site is a CMS website in the everyday sense: you edit content in a dashboard, store it in structured collections, and publish it through templates. The caveat is that the CMS is a feature of the Wix platform, not a separate piece of software you can install, host or swap out. The pieces are the Wix CMS (formerly called Content Manager), dynamic pages, the Wix Blog app, Velo for code (always on in Wix Studio, a Dev Mode switch in the regular Wix Editor), and a separate Wix Headless product for people who want their own frontend. Everything runs on Wix's servers, and Wix's own help center says so in as many words.

Disclosure: I work on VeloCMS, which shows up in the comparison section. It gets an entry about the same size as everyone else's, weaknesses included, and there's a section near the end on when it's the wrong pick.

Last verified: 2026-10-09.

Method: prices, limits and features come from the vendors' own pages, read on 2026-10-09, and each links to its source inline. Where a page gave no number, I say so. Opinions are marked as mine.

What does "CMS" mean, and how does Wix fit it?

A content management system separates what a site says from how it looks. You keep content (posts, products, listings) in a structured store, design templates once, and the system pours the first into the second. WordPress, Ghost and Webflow all work that way. So does Wix, once you use its CMS.

Where Wix differs is packaging. With WordPress.org you download software, put it on a host and run it. With Wix there's nothing to install and nothing to patch, because the builder, the database, the hosting and the editor are one product. Wix's developer docs describe the Wix CMS as "a built-in document-oriented database optimized to store and retrieve website content" that is "globally replicated" and "fully managed by Wix." Around it sit datasets (invisible components that wire page elements to data), dynamic pages and a Data API.

An independent tracker treats Wix as a CMS, too. W3Techs lists it in its content management category and put it at 4.2% of all websites in its October 2026 report, behind WordPress at 40.1% and Shopify at 5.4% (W3Techs, accessed 2026-10-09).

So the honest short version: Wix is a website builder first, and a CMS is one of the things inside it. If your question is "can I manage structured content on it," yes. If it's "can I treat it like a standalone CMS I can move around," mostly no, and the rest of this post is about why.

What can you actually manage with the Wix CMS?

You manage collections. A collection is a database table with typed fields, and you can view it as a table, list or gallery. Wix's CMS overview (accessed 2026-10-09) lists permissions on who can view, add, edit or delete, saved views, indexes, backups to restore earlier collection versions, and a sandbox for testing before you go live. It also supports CSV import and export.

The payoff is dynamic pages. You design one page layout and Wix generates a page per collection item, with the URL deciding which item to show. Wix's docs describe list pages, item pages and category pages, and the item-page version gives "every collection item a unique URL." The same overview gives a total pages quota of 298, up to 100 of them static. Each dynamic page you add counts as one page, but the page says dynamic pages can generate unique URLs for every item in a collection without consuming additional pages, so the item caps below are the limit that bites.

Wix's own apps use the same machinery: Stores and Bookings write their data to collections. These app collections are read-only in the CMS (edits happen in the app), can be exported to CSV, and don't count toward the item cap, per the data limits page.

Blogging is its own app. Wix Blog covers multiple writers with assigned roles, categories, hashtags, comments and likes, SEO and AI tools, translations, subscription options for members-only posts and blog analytics. Wix's developer docs say a blog can hold up to 100,000 posts, and a post can sit in up to 10 categories.

How many items can a Wix site hold on each plan?

This is the number people find out too late. From Wix's collection limits page (accessed 2026-10-09), items across your collections:

• Free site: 1,000 items on a regular account, 10,000 if the site belongs to a Wix Studio account
• Light: 1,500 items
• Core: 4,000 items
• Business: 20,000 items
• Business Elite and Elite: 10,000,000 items

Database storage is 10 GB across Light, Core and Business, and 100 GB on Business Elite and Elite (effective January 7, 2026). Each item is capped at 512 KB across its fields combined, excluding media files. One gotcha from the data feature limitations page: if you downgrade, nothing is deleted, but you can't add items until you're back under the lower quota.

What are Wix Studio and Velo for developers?

Wix sells more than one editor. The regular Wix Editor is for site owners, while Wix Studio is pitched at agencies and professionals building client sites. Velo is the development layer in both: Wix describes it as "an open development platform" where you "work in Wix's visual builder, add custom functionality and interactions using Velo's APIs, use your own tools, and enjoy serverless coding in both the front-end and backend." In the regular editor you turn it on with Dev Mode in the top bar. In Studio, per the Wix Studio coding docs, coding is always available.

Once you're in, the docs describe frontend and backend JavaScript (backend files become web modules your pages call), data hooks, scheduled jobs and custom routers, npm packages, outside calls with fetch, a secrets manager, HTTP functions for your own endpoints, and external databases connected through an adapter so they look like ordinary collections.

There are three places to write it: the built-in Code panel for small jobs, the browser-based Wix IDE (VS Code-based) for bigger projects, and a local setup where the Git integration and Wix CLI connect the site to GitHub so you can work in your own editor and publish from the command line. The Wix IDE can't be used while GitHub integration is on, though you can disconnect and switch back.

The compute side has real ceilings. On a free site, per Wix's free-site limits, you get one micro backend container (1 vCPU, 400 MB of RAM), 60 backend requests a minute and a 14-second timeout. Data requests are capped at 1,000 reads and 60 writes a minute, and the data limits page adds that each include() in a query counts toward the request quota (its own example query counts as 3 reads). Paid plans raise these, but neither Wix's data-limits nor compute-limits page prints per-plan numbers for requests, only the free-tier table above, so check Wix's plan comparison before you size a project.

My take: Velo is a real development environment, handy for bolting a custom form handler onto a site a non-developer will keep editing. It's not the place to port a large application, and the quotas say so.

Can you use Wix as a headless CMS?

Partly, and it depends what you mean by headless. Wix Headless lets you "build a custom frontend on any stack you choose and power it with production-ready Wix business APIs," and the list of solutions it names includes eCommerce, bookings, events, memberships, CMS and blog.

There are two routes. Wix recommends Wix-managed headless, where Wix hosts and runs your frontend; build it with Astro and you also get automatic authentication, SEO support and extensions. In self-managed headless you host wherever you like, call Wix from the JavaScript SDK or REST API, and handle authentication yourself (so does any managed setup that isn't Astro). Wix says Headless is free to start, with a premium plan unlocking payments, custom domains and more.

For a blog, the Posts API is the relevant piece. The docs list endpoints to get, list and query posts, and listing returns up to 100 published posts per request. Reads need the Read Blog permission scope, and you can create admin API keys in the API Keys Manager, scoped to all sites or only the ones you select (how to generate one).

What it isn't: a classic content API you can point a static site at and forget. Your content still lives in Wix, Wix's data quotas apply to anything making data requests, and you depend on Wix's auth model. If you want Git-backed Markdown that runs anywhere, that's a different category of tool.

What are the real limits of Wix as a CMS?

Can you export or move a Wix site?

This is the limit that matters most. Wix's help article on exporting says it plainly: "Since Wix is a SaaS solution, your site must run on Wix's servers." You can connect a domain you bought elsewhere (paid plan needed), and the article says the content belongs to you, but the site itself stays on Wix. There's no zip of HTML, CSS and a database to carry to another host.

For content, the picture is patchy:

• Blog posts: Wix's help center lists exporting posts to other platforms as a feature request and says it is currently not possible. The blog's RSS feed shows only the latest 20 posts, so it won't carry an archive.
• CMS collections: they do export. From More Actions you choose Export to CSV, and you can export everything (including hidden and system fields), only the rows matching a filter, or just the structure. Non-Latin text is UTF-8 and time fields come out as UTC+0, per Wix's export guide. That page doesn't say how media fields or reference fields are written out, so test with a small collection before you rely on it.
• Images and video: the Media Manager lets you download files you uploaded, several at a time within a folder, but not everything in one click, and free Wix and Shutterstock media can't be downloaded.
• Redirects: the redirect manager imports up to 500 redirects per CSV file and exports your whole list.

Getting in is easier than getting out. Wix's WordPress importer takes up to 5,000 posts per run, from a blog URL or an XML file, with an overall Wix Blog cap of 100,000. It brings text, images, video, original dates, alt text and categories. It skips tags, author names, comments, forms, plugins, custom code and attached documents. Notice the asymmetry.

What about SEO controls?

Wix's SEO features page (accessed 2026-10-09) lists an editable robots.txt, automatic structured data for products, events and blog posts that you can customize, editable canonical tags, title and meta description control, open graph tags, editable URL slugs on pages, product pages and blog posts, and a URL Redirect Manager for 301s. You work through Wix's settings screens and, if you code, Velo, not server configuration.

And performance?

Third-party field data is kind to Wix. The Core Web Vitals tracker at corewebvitals.io reports Q2 2026 mobile data in which 94.4% of Wix sites passed Largest Contentful Paint (p75 of 1.6 s) against 69.5% for WordPress (2.7 s) and 85.8% for Squarespace (2.2 s). Webflow and Ghost showed 100% from tiny samples (15 and 37 sites). It compares populations, not your site.

What other limits should you plan around?

Collection caps by plan, covered above, and a CMS request timeout of 5 seconds on most plans (10 seconds on Business Elite and Elite), so a slow aggregate query fails instead of limping along. Sandbox and live collections also have to be synced deliberately, and Wix warns a sync can't be undone. None of that hurts a brochure site or a modest blog. It bites where you'd normally reach for a real database.

How much does Wix cost right now?

From wix.com/plans (accessed 2026-10-09), shown in USD per month with yearly billing paid in full at purchase:

• Free: $0, with a Wix address. Wix says a free site has 500 MB of storage and 1 GB of bandwidth, shows Wix ads, and needs an upgrade to connect a custom domain
• Light: $17.77 a month, 2 GB storage, 2 site collaborators
• Core: $29.77 a month, 50 GB storage, accept payments, basic eCommerce, scheduling and services, 5 collaborators
• Business: $39.77 a month (marked Recommended), 100 GB storage, standard eCommerce, 10 collaborators
• Business Elite: $159.77 a month, unlimited storage, advanced eCommerce, 100 collaborators

The page contradicts itself on tax. Each card says "Price includes GST," while the footnote says "Prices and currency vary by location. USD prices displayed for reference only," and adds that prices do not include applicable taxes, which are set by your billing address. A Wix blog post lists the same four plans as $17, $29, $39 and $159. So treat the cents as noise and read the number on the purchase page, which Wix says shows the final price before you pay. Wix offers a 14-day money-back guarantee, and selected yearly plans come with a one-year free domain voucher (first purchase of a site plan only, usable on a new domain or a domain transfer).

Wix Studio has its own site plans, named Basic, Standard, Plus and Elite. Wix's help page lists their allowances (CMS items match the numbers above, with 3, 5, 10 and 100 client accounts) but no prices, and the Studio plans page shows none in the HTML I could read. Wix's own blog posts disagree with each other on Studio prices (Basic at $12 in one, $19 in another), so I won't quote any.

When is Wix the right CMS, and when should you pick something else?

Wix is a strong pick when you want a good-looking site with a blog, bookings or a small shop, the owner edits it, and nobody wants to maintain hosting. It's weaker when portability matters, when your content runs into the item caps above, or when your workflow is code-first. Each entry below covers what it's good at, what it costs and what you give up.

WordPress.org (self-hosted)

WordPress.org is free software under the GPLv2 or later, built on PHP and MariaDB, and runs on whichever host you pick. That's the opposite of Wix on ownership: you hold the files and the database, with a huge plugin and theme ecosystem. The software is free, hosting is a separate bill from whichever host you pick, and patching and backups are yours.

WordPress.com

WordPress.com is managed WordPress. Its pricing page (accessed 2026-10-09) shows a Free plan with 1 GB and a WordPress.com subdomain, and USD prices that drop with longer commitments: Personal $9 monthly or $4 a month yearly, Premium $18 or $8, Business $40 or $25, and Commerce $70 or $45. It advertises more than 60,000 plugins on its paid plans. You get the WordPress content model with someone else running the servers, and the trade-off is working inside WordPress.com's plan and hosting rules. Its export produces a standard XML file with posts, pages, comments, categories and tags, but only links to your media, which you download separately from the media library.

Squarespace

Squarespace is the closest rival to Wix for design-led sites. It showed me pounds: Basic £12 a month yearly (£16 monthly), Core £17 (£24), Plus £29 (£36) and Advanced £79 (£89), with a 14-day free trial. Core and above add custom CSS and JavaScript. Fees apply on commerce: 2% on online-store sales at Basic and a 7% fee on digital content and memberships at Basic, falling to 0% at Advanced. Like Wix it's a closed platform, and its export is an XML file that covers one blog page with its posts and layout pages (plus gallery pages on 7.0 sites), but not store pages, product blocks, drafts or custom CSS.

Webflow

Webflow is the designer's tool with a real CMS behind it. As of 2026-10-09 it lists a free Starter plan (webflow.io domain, 50 CMS items), Basic at $15 a month billed yearly (no CMS), and Premium at $25 a month billed yearly with 20,000 CMS items and 40 collections. Prices are per site, in USD, plus tax. Its collections are the draw, though Wix's CMS has reference fields too, so the difference is mostly layout control rather than data modeling. The catch, in my experience: it has a steeper learning curve than Wix, Premium bandwidth comes in tiers from 50 GB up to 2.5 TB, and its code export is HTML and CSS only. The pricing page says dynamic content (CMS items and pages) can't be exported.

Ghost

Ghost is a publishing platform, not a site builder. Ghost(Pro) is $18 a month billed yearly for Starter (1,000 members, one staff user), $29 for Publisher (three staff users, custom themes, paid subscriptions, 0% Ghost transaction fee) and $199 for Business (15 staff users), all USD. It's MIT-licensed on GitHub, so you can self-host, and Ghost's hosting docs say self-hosters take on weekly updates and server maintenance. (The hosting docs say Ghost(Pro) is "from $15" a month, which I couldn't reconcile with the pricing page's $18, so I use the pricing page and you should check at checkout.) It's superb at writing, newsletters and memberships. It's not the tool for a bookings page or a general-purpose brochure site.

VeloCMS

VeloCMS is a hosted blog-first platform that also does newsletters, memberships and a small store. Its pricing page (accessed 2026-10-09) lists Pro at $9 a month, Business at $29 and Agency at $69, with yearly billing taking 20% off. Pro includes a custom domain, a block-based page builder, newsletter, membership paywall, ecommerce, 5 GB of storage and 5,000 subscribers; payments go through your own payment-provider account, so VeloCMS takes no platform fee, although the provider's processing fees still apply. Every plan is paid; the way to try it is a 14-day trial, with a card taken at signup and no charge until day 15. The trade-offs are real: it's young, the marketplace page advertises 57 free integrations (all first-party) and the themes page 40 themes, it's managed SaaS only with no self-hosted edition, and the developer page says third-party plugin development isn't open yet. Content exports as JSON or CSV.

How do you check what you can get out of Wix, or move off it?

Do this before you build anything big, and again before you leave.

1. Write down your live URLs. Pull the sitemap and note every blog post address exactly as it appears on the live site, because your new platform's redirect map starts from that list.
2. Export every collection to CSV, including hidden and system fields, and check how images, rich text and reference fields look.
3. Get the blog posts out by the least bad route. With no post export, your options are scraping the live pages, the 20-post RSS feed, or an API key plus the Posts API. I haven't run the API route on a large blog, so spot-check rich content for fidelity.
4. Download media you uploaded, folder by folder. Free Wix and Shutterstock images aren't downloadable, so plan replacements.
5. Export your redirect list, if you have one.
6. Plan the cutover. A redirect set up in Wix can only answer requests that reach Wix, so once DNS moves, the 301s must live on the new host. Keep the Wix plan alive until the new site is verified.
7. Accept what stays behind: the design, forms, bookings, member areas, app data and any Velo code that depends on Wix APIs. You'll rebuild those.

If you're heading to VeloCMS, its Wix import guide says it reads your public site, so no login or API key is needed. It brings posts from the blog feed, pages found via the sitemap, store products and images (re-hosted), up to 30 pages per run, arriving as drafts. Content behind a login, dynamic pages, and Wix-specific blocks such as forms, bookings and members areas can't be read that way, your design doesn't transfer, and the guide doesn't mention redirects or custom slugs. Other targets have their own import paths. Check the target's guide for the same list of what is skipped.

Who is each option best for?

• Wix: owners who want to design visually and run a blog, bookings or a small shop on one subscription, and don't plan to move later.
• WordPress.org: people who need a particular plugin, want full ownership and accept the maintenance.
• WordPress.com: people who like WordPress and want the hosting handled, and can live with the platform's plan structure.
• Squarespace: design-led small businesses that want a polished site and a simple editor, and are comfortable with a closed platform.
• Webflow: designers who want structured CMS collections with precise layout control, and will learn the tool.
• Ghost: writers and publishers whose business is the newsletter and paid membership, with no need for a store or a page builder.
• VeloCMS: solo creators and small teams who want a blog, newsletter, membership and small store in one hosted login, and don't need a big plugin ecosystem.

When is VeloCMS the wrong choice?

Sometimes. If you want a third-party app market, Wix has one and VeloCMS doesn't yet, since its integrations are all first-party. (It lists a booking integration, but I haven't compared it feature by feature with Wix Bookings.) If you want self-hosting or source access, it's out: the application is proprietary. If you want a permanent no-cost tier to test with, it has none, only the card-backed trial. If your site depends on a specific WordPress plugin, it won't run there. And if you want content as Markdown files in Git, that's a different category of tool.

FAQ

Is Wix a CMS or a website builder?

Both. Wix is a hosted website builder, and the Wix CMS is a feature inside it that stores structured content in collections and drives dynamic pages. The docs still say "CMS (formerly Content Manager)" in many places, which is the old name.

Is the Wix CMS free?

Wix has a free plan, and the free-site limits let you try most data and coding features, with a cap of 1,000 items on a regular free site. Collections grow with the plan: Light 1,500 items, Core 4,000, Business 20,000.

Can I export my Wix blog?

Wix's help center says exporting blog posts to other platforms isn't currently possible. You can export CMS collections as CSV, pull the latest 20 posts through RSS, or read posts through the Posts API with an API key. Download your media separately.

Can I use Wix with my own frontend?

Yes, through Wix Headless. Either Wix hosts your frontend (its recommended path, with automatic authentication if you use Astro) or you host it yourself and call Wix over the JavaScript SDK or REST API. Your content and business data still live in Wix.