QUICK ANSWER
What is the best no-code website builder in 2026?
There is no single best no-code website builder for every site. Choose Playcode for a prompt-led custom site that may grow into application workflows; Carrd for a focused one-page site; Framer or Webflow for design-led production; Wix or Squarespace for managed site tools; Hostinger for a bundled hosting path; Shopify for commerce-first operations; and WordPress.com for managed WordPress publishing. Verify current plan, export, and recovery limits before buying.
A no-code website builder can mean a prompt-led custom build, a hosted visual editor, a theme-driven store, or a focused one-page tool. Those products do not create the same output or leave the buyer with the same publishing, export, recovery, collaboration, and recurring-cost boundary.
Playcode publishes this guide and appears first for disclosure, not as a declared winner. The other products are alphabetical. We reviewed dated first-party documentation and froze one reproducible service-business website brief, but we did not run that brief in all nine products. Every benchmark output hash therefore remains empty and the page reports no hands-on winner.
How this comparison works
The shortlist is organized around documented operating boundaries. Fit statements are editorial deductions from those boundaries, not vendor ratings, performance tests, or guarantees.
Define the website job before the product
Name the required pages, content records, form or commerce path, editors, custom domain, and handoff owner. A one-page profile, content publication, online store, and database-backed workflow should not share one undefined score.
Sources: [carrd-overview], [shopify-online-store], [wordpress-com-vs-org], [playcode-builder]
Read the current first-party boundary
Use official product, help, pricing, hosting, export, recovery, and ownership documentation. Record the access date, region, billing term, plan, add-ons, and exclusions instead of copying an undated starting price.
Sources: [wix-plan-pricing], [squarespace-plans], [webflow-pricing], [framer-pricing], [hostinger-plans]
Separate build, production, and exit meters
Price creation and revision separately from the live site. Then inventory code, content, products, runtime records, media, domains, accounts, secrets, and providers as distinct exit assets.
Sources: [playcode-pricing], [wix-export], [squarespace-export], [webflow-export], [framer-export], [hostinger-export], [shopify-product-export], [wordpress-com-export], [carrd-download]
Freeze one acceptance case
Use the exact service-business-website-v1 brief and require all ten checks: AT-01 Clean published page; AT-02 Responsive layout; AT-03 Navigation and canonical; AT-04 Independent content edit; AT-05 Quote form states; AT-06 Search metadata; AT-07 Keyboard and structure; AT-08 Exit boundary recorded; AT-09 Recovery rehearsed; AT-10 Meters and interventions recorded. The brief is 1083 characters and the output contract is 724 characters before normalization.
Sources: [playcode-cloud], [wix-history], [webflow-backups], [framer-staging]
Refuse a winner without comparable outputs
A product run is comparable only when the same brief passes every acceptance check and produces the required normalized hashes. Screenshots, marketing examples, source documentation, and a successful first publish are not substitutes for the missing record.
Sources: [hostinger-backups], [shopify-theme-copy], [squarespace-ownership], [wix-transfer], [framer-transfer]
What this page owns
This owner answers the dated editorial shortlist question. Commercial build intent, AI-only comparisons, ease-first comparisons, app builders, and audience-specific website decisions keep their existing owners.
Included
- Nine no-code website authoring and publishing paths with documented product boundaries.
- Authoring, output, content, business workflow, publishing, export, recovery, collaboration, build-meter, and production-meter decisions.
- A fixed fictional service-business website brief that a buyer can reproduce later.
- Current first-party documentation with explicit access dates and a near-term review date.
Not included
- Generic commercial “no code website builder” intent owned by /no-code-website-builder.
- AI-only website-builder rankings owned by /best-ai-website-builders.
- Ease-first selection owned by /blog/easiest-website-builders-2026.
- Small-business audience selection owned by /blog/best-website-builder-small-business-2026.
- No-code application builders owned by /blog/best-no-code-app-builders-2026.
- Observed speed, uptime, support quality, accessibility, conversion, security, or generated-design quality without completed tests.
Ten boundaries to compare
These criteria are deliberately non-scoring. A buyer can reject a product on one essential boundary even when it offers more features elsewhere.
Authoring model
Separates prompt-led, template-led, section-based, and visual-canvas workflows without treating any one interface as universally easier.
Website output
Defines whether the result is a hosted site, an online store, a one-page site, project code, or a site that can grow into application behavior.
Content and SEO
Checks repeatable content, page metadata, URL control, and the boundary between built-in features and work the site owner must design or verify.
Business workflows
Makes forms, commerce, members, apps, databases, and external providers explicit instead of assuming every website plan includes the same operating system.
Domain and publishing
Shows what the platform hosts, which plan connects a custom domain, and what still needs DNS, provider, review, or release work.
Ownership and export
Keeps project code, site content, product records, live data, domains, accounts, secrets, and provider configuration as separate exit paths.
Recovery boundary
Distinguishes an editor undo or version from a restorable published site, content export, live-data restore, and independently runnable copy.
Collaboration and handoff
Checks who can edit and publish, who owns billing, and whether a client or successor can receive the site and its dependent services.
Build meter
Records the unit consumed while creating and revising the site, such as AI credits, editor seats, site slots, apps, or implementation time.
Production meter
Prices the live month using the site plan, traffic, storage, content, transactions, apps, seats, providers, domains, and renewal terms that actually apply.
Nine no-code website-builder paths
Playcode appears first because it publishes the guide; the remaining products are alphabetical. Item order is not a ranking. Every finding below is limited to the cited first-party source set.
Playcode
Best for: A non-technical team that wants a prompt-led custom website and a documented path to backend, database, or application behavior when the project grows.
Playcode combines plain-language and visual iteration with Playcode Cloud. The important boundary is to keep exported project code separate from live records, credentials, domains, and provider configuration.
| Criterion | Finding |
|---|---|
| Authoring model | The documented website workflow begins with a plain-language description and supports later chat and visual changes. The buyer still owns the brief, content accuracy, and final review. Sources: [playcode-builder] |
| Website output | The website path can publish a public site, while Playcode Cloud documents backend, database, files, and other runtime behavior when the project needs more than static pages. Sources: [playcode-builder], [playcode-cloud] |
| Content and SEO | Pages, content structures, metadata, and search behavior belong to the generated project rather than a universal fixed CMS contract. Verify the actual URLs, metadata, structured data, editing path, and rendered output before release. Sources: [playcode-builder], [playcode-cloud] |
| Business workflows | Cloud documents backend, database, files, jobs, and WebSockets. Authentication, authorization, form delivery, payment, and provider rules remain application-specific work and may require external accounts and credentials. Sources: [playcode-cloud] |
| Domain and publishing | Current product and pricing pages document hosted publication and custom domains under applicable plan limits. Domain ownership, DNS access, final checks, and external-provider setup remain buyer responsibilities. Sources: [playcode-builder], [playcode-pricing] |
| Ownership and export | Current paid-plan documentation includes project-code export. Treat live database records, files, secrets, domains, analytics, and external-provider state as separate migration assets. Sources: [playcode-pricing], [playcode-cloud] |
| Recovery boundary | Playcode Cloud documents snapshots and rollback for supported project state. A recovery rehearsal must still confirm the chosen snapshot, retention, permissions, provider state, and the production action that restores service. Sources: [playcode-cloud] |
| Collaboration and handoff | Plan and project access determine collaboration. A client handoff should inventory the Playcode project, billing, domain, exported source, live data, secrets, and every external account rather than treating one project role as the whole transfer. Sources: [playcode-pricing], [playcode-cloud] |
| Build meter | AI work is metered in credits under the current pricing model. Record the plan, credit balance, selected model or mode, failed attempts, and manual interventions for the frozen brief. Sources: [playcode-pricing] |
| Production meter | Price the live site or app using the current plan, Cloud app and capacity limits, domain, traffic, storage, external providers, and operating work rather than the AI-credit meter alone. Sources: [playcode-pricing], [playcode-cloud] |
Tradeoffs
- The guided custom path reduces dependence on a fixed template while requiring the team to review the generated site and its application-specific rules.
- AI credits and Cloud limits are separate planning inputs; a project-code export is not a complete live-system migration.
- There is no theme gallery to choose from. The starting point is a written brief, which suits a custom site and not a buyer who wants a ready-made design to edit.
Carrd
Best for: A manually arranged profile, launch page, link page, or focused landing page whose information architecture can remain one page.
Carrd documents a canvas for one-page sites, plan-gated domains and forms, account sharing and transfer, and a Pro Plus source download with important portability limits.
| Criterion | Finding |
|---|---|
| Authoring model | Carrd documents a visual canvas where the owner adds and arranges elements, edits properties, previews, and publishes from a template or blank starting point. Sources: [carrd-overview] |
| Website output | The product scope is a responsive one-page site. Named sections can switch in place to simulate multiple pages, but they do not establish a separate multi-page content architecture. Sources: [carrd-overview], [carrd-sections] |
| Content and SEO | The reviewed product and plan documentation centers on manually composed one-page sites rather than a structured multi-author CMS. Validate metadata, repeatable content, redirects, and editorial workflow against the exact plan and site. Sources: [carrd-overview], [carrd-plans] |
| Business workflows | Plan-gated forms can send data to email, URLs, automation services, or custom code. Those destinations, credentials, data handling, retries, and provider costs remain separate operating boundaries. Sources: [carrd-forms], [carrd-plans] |
| Domain and publishing | Eligible Pro plans support custom domains with documented DNS setup and SSL. The domain and its DNS account remain separate from the Carrd site slot. Sources: [carrd-domain], [carrd-plans] |
| Ownership and export | Pro Plus can download site source, but platform-dependent forms stop working outside Carrd and the downloaded result cannot be imported back. Content, form submissions, domain, and provider state need separate handling. Sources: [carrd-download] |
| Recovery boundary | The reviewed download path is an exit artifact, not a round-trip restore because it cannot be re-imported. Record a separate Carrd-side recovery method and test it before relying on the download. Sources: [carrd-download] |
| Collaboration and handoff | Sharing grants another Carrd user editor access, while a documented transfer changes ownership to an eligible Carrd account. Domain, provider, form destination, and billing handoffs still need their own checklist. Sources: [carrd-transfer] |
| Build meter | The documented build boundary is plan-gated site slots and features rather than a universal AI-generation meter. Record the Pro tier, number of sites, paid features, and manual build time. Sources: [carrd-plans] |
| Production meter | Price the selected Pro tier, site allowance, custom domain, forms, embeds, and any connected automation or payment service. Do not infer the live cost from Carrd plan price alone. Sources: [carrd-plans], [carrd-forms], [carrd-domain] |
Tradeoffs
- A focused one-page model keeps the site compact but is a poor fit when a real multi-page content system or durable application workflow is already required.
- Advanced forms, custom domains, embeds, sharing, transfers, and downloads depend on the selected Pro tier.
- A downloaded site cannot be imported back into Carrd, and Carrd-dependent forms stop working outside the platform.
Framer
Best for: Design-led marketing teams that value a direct visual canvas, motion, managed publishing, and a compact site workflow more than off-platform HTML export.
Framer packages visual composition, CMS limits, managed hosting, staging on applicable plans, collaboration, and AI credits around a site subscription. Published sites remain dependent on Framer services.
| Criterion | Finding |
|---|---|
| Authoring model | Framer centers work on a direct visual canvas with responsive layouts, components, motion, CMS content, and managed publishing. Applicable plans add staging and version controls. Sources: [framer-pricing], [framer-staging] |
| Website output | The documented output is a Framer-hosted site on a Framer or custom domain. The current export documentation says published sites depend on Framer rendering, optimization, and caching services. Sources: [framer-export], [framer-staging] |
| Content and SEO | Current site plans define pages, CMS collections and items, bandwidth, and other publishing allowances. Verify the required schema, URL, metadata, locale, and editorial access against the selected plan. Sources: [framer-pricing] |
| Business workflows | The reviewed pricing boundary centers on marketing-site publishing, CMS, localization, testing, and site services. Treat forms, commerce, members, databases, and external providers as separate requirements to verify. Sources: [framer-pricing] |
| Domain and publishing | Framer supports managed publishing and custom domains, while applicable plans add staged versions before deployment. Record DNS authority and the person allowed to deploy. Sources: [framer-staging], [framer-pricing] |
| Ownership and export | Framer explicitly does not provide standalone HTML export for self-hosting. A project transfer can change the Framer owner, but that is different from receiving an independently runnable website. Sources: [framer-export], [framer-transfer] |
| Recovery boundary | File history stores view-only snapshots from which content can be copied, and published versions can be selected for rollback. Neither mechanism creates an off-platform HTML restore. Sources: [framer-version-history], [framer-staging], [framer-export] |
| Collaboration and handoff | Framer documents workspace and project roles plus granular design, content, and deploy permissions. Project transfer changes ownership and can require the recipient to select a new site plan. Sources: [framer-roles], [framer-transfer] |
| Build meter | Current plans meter editors and AI-agent credits alongside site allowances. Record the site plan, billed roles, AI use, add-ons, manual work, and failed attempts for the fixed brief. Sources: [framer-pricing], [framer-roles] |
| Production meter | Price the site plan, pages, CMS records, bandwidth, editors, locales, testing, and add-ons. Bandwidth documentation describes notifications, upgrades, and ongoing overage handling. Sources: [framer-pricing], [framer-bandwidth] |
Tradeoffs
- Managed publishing removes separate hosting setup while Framer explicitly does not provide standalone HTML export for self-hosting.
- CMS, bandwidth, AI credits, editors, localization, testing, and advanced hosting can introduce separate limits or charges.
- File history, published versions, project transfer, and an independently runnable site copy are different recovery and ownership mechanisms.
Hostinger Website Builder
Best for: A buyer who wants the website builder packaged with a Hostinger hosting plan and is willing to verify promotion, renewal, export, and account boundaries carefully.
Hostinger currently packages a drag-and-drop builder, AI tools, hosting, domains, storage, backups, and ecommerce features inside hosting plans. Promotional term and renewal price are separate, and the documented content export is partial.
| Criterion | Finding |
|---|---|
| Authoring model | Hostinger currently presents drag-and-drop website building and AI tools inside its hosting plans. Record which builder or AI path the account actually opens rather than treating every bundled tool as one workflow. Sources: [hostinger-plans] |
| Website output | The documented package produces a hosted website inside the selected Hostinger plan. Current plan descriptions include site counts, storage, domain, backup, ecommerce, and AI-tool boundaries. Sources: [hostinger-plans] |
| Content and SEO | The export guide can move regular pages, text, images, and supported files to WordPress, while explicitly excluding layout, store, forms, submissions, integrations, and SEO settings. Verify the live content and metadata model directly. Sources: [hostinger-export] |
| Business workflows | Current plan descriptions include integrated ecommerce, email, and AI tools, but they do not establish every payment, form, submission, inventory, or provider rule needed by the fixed brief. Confirm those in the selected account. Sources: [hostinger-plans], [hostinger-export] |
| Domain and publishing | Current annual-plan descriptions include a domain for a limited period and hosted publication. Record the domain owner, DNS access, included term, later renewal, and site plan separately. Sources: [hostinger-plans] |
| Ownership and export | Hostinger documents a partial content export to an existing WordPress site. It does not export the complete website layout, store, integrations, forms, submissions, or SEO settings through that path. Sources: [hostinger-export] |
| Recovery boundary | Builder backups are created after publication and after updates, stored for a documented retention period, and restored inside the editor. Confirm retention and restore access in the selected account before relying on them. Sources: [hostinger-backups] |
| Collaboration and handoff | The reviewed builder source set documents hosting, partial export, and editor backups, but not a complete builder-site account-transfer contract. Record account, domain, billing, email, store, and provider handoff as unresolved until verified. Sources: [hostinger-plans], [hostinger-export] |
| Build meter | The public plan page packages builder and AI features inside the hosting purchase. Record the selected plan, term, included AI allowance, failed attempts, and manual work instead of assuming unlimited generation. Sources: [hostinger-plans] |
| Production meter | Price the promotional commitment and renewal separately, then include site count, storage, backups, domain renewal, email, ecommerce, and any external provider. Promotional monthly equivalents are not the ongoing monthly contract. Sources: [hostinger-plans] |
Tradeoffs
- Bundling can reduce initial setup choices while making the hosting plan, term, renewal, site count, storage, backup cadence, email, and builder features one purchase decision.
- The WordPress export path omits layout, store, integrations, forms, submissions, and SEO settings.
- Builder backups are platform versions, not a documented independently runnable file-and-database archive.
Shopify
Best for: A commerce-first website where products, inventory, checkout, orders, fulfillment, apps, and store ownership are the central operating system.
Shopify combines an online store, themes, pages, blog, catalog, checkout, fulfillment, apps, and managed hosting. It should be shortlisted for a store job, not because every general website needs a commerce platform.
| Criterion | Finding |
|---|---|
| Authoring model | Shopify uses a theme-based online-store editor with configurable sections and blocks, plus pages, navigation, blog, and theme-code paths where supported. Sources: [shopify-online-store], [shopify-themes] |
| Website output | The documented output is a hosted online store with products, pages, blog, navigation, search, custom domains, and checkout. Custom storefronts are a separate implementation boundary. Sources: [shopify-online-store], [shopify-products] |
| Content and SEO | Shopify documents pages, blog, product and collection records, navigation, and search inside the online-store model. Verify URL, metadata, redirects, editorial roles, and structured data on the chosen theme and plan. Sources: [shopify-online-store], [shopify-products] |
| Business workflows | Products, inventory, checkout, orders, fulfillment, and apps are first-class operating surfaces. Each installed app retains its own permissions, billing, data, support, and uninstall boundary. Sources: [shopify-products], [shopify-apps] |
| Domain and publishing | The Online Store supports hosted publication and custom domains. Theme publication, DNS, payment setup, shipping, taxes, and provider readiness remain separate launch checks. Sources: [shopify-online-store], [shopify-themes] |
| Ownership and export | Shopify documents product CSV export for backup and migration, with image and inventory boundaries. A store transfer has separate domain, billing, app, payout, tax, payment-provider, and permission work. Sources: [shopify-product-export], [shopify-transfer] |
| Recovery boundary | A theme can be duplicated before edits, but that protects theme state rather than the complete store. Products, orders, customers, apps, settings, payments, and external providers require separate backup and recovery plans. Sources: [shopify-theme-copy], [shopify-product-export], [shopify-apps] |
| Collaboration and handoff | Store ownership can transfer, but Shopify documents a wider checklist for contacts, domains, billing, apps, payouts, taxes, payment providers, and permissions. Use that checklist for client handoff. Sources: [shopify-transfer] |
| Build meter | The reviewed sources meter work through the selected plan, theme, apps, and implementation effort rather than one universal site-generation score. Record paid theme, app, and manual work separately. Sources: [shopify-pricing], [shopify-themes], [shopify-apps] |
| Production meter | Price the local plan, payment and transaction path, apps, theme, domain, catalog size, fulfillment, and operator work. Shopify advises confirming current local plan terms in the account. Sources: [shopify-pricing], [shopify-apps], [shopify-products] |
Tradeoffs
- The commerce operating model is deep, while a content-only service site may inherit product, app, payment, and operational complexity it does not need.
- Plan, payment, app, theme, domain, and fulfillment costs can sit outside one headline subscription.
- Product CSV export and store ownership transfer do not automatically move the complete theme, apps, orders, customers, payments, domains, or provider state.
Squarespace
Best for: A team that wants a managed section-and-block website, integrated content and commerce surfaces, and a focused set of official integrations.
Squarespace combines AI starting points, Fluid Engine editing, managed hosting, plan-based site and commerce features, integrations, site ownership transfer, and partial content exports.
| Criterion | Finding |
|---|---|
| Authoring model | Squarespace documents Blueprint AI and AI templates as starting paths, followed by its visual site system. Fluid Engine is the version 7.1 drag-and-drop editor for block sections. Sources: [squarespace-ai], [squarespace-fluid-engine] |
| Website output | The output is a Squarespace-hosted website under one site plan. Squarespace does not host a site built on another platform, so an external move uses supported exports plus a rebuild. Sources: [squarespace-hosting], [squarespace-export] |
| Content and SEO | Current plans and the visual editor define supported page, contributor, code, and content boundaries. Verify the required collection types, URLs, metadata, redirects, and editorial access in the selected account. Sources: [squarespace-plans], [squarespace-fluid-engine] |
| Business workflows | Current plans can add commerce, while official integrations span forms, domains, social, analytics, and other site jobs. Some services and extensions are separately paid and supported. Sources: [squarespace-plans], [squarespace-fees], [squarespace-integrations] |
| Domain and publishing | All Squarespace plans include hosting and bandwidth for the Squarespace site. Domains, payment accounts, and some attached services remain separate ownership and renewal surfaces. Sources: [squarespace-hosting], [squarespace-ownership] |
| Ownership and export | Site ownership can transfer to an accepted contributor. Site export uses WordPress XML for selected content and excludes many page, style, store, draft, and media elements; products use a separate CSV path. Sources: [squarespace-ownership], [squarespace-export], [squarespace-product-export] |
| Recovery boundary | The reviewed source set documents ownership transfer and partial exports, not an independently runnable full-site archive. Confirm editor history and restore scope in the selected account, then keep export as a separate exit record. Sources: [squarespace-ownership], [squarespace-export] |
| Collaboration and handoff | Plan choice controls contributor and code boundaries, and one accepted contributor can become owner. Billing, domains, payment accounts, attached services, and prior-owner permissions still require review. Sources: [squarespace-plans], [squarespace-ownership] |
| Build meter | The reviewed sources place AI assistance and visual editing inside the site-plan workflow rather than one comparable per-site generation score. Record contributors, AI use, custom code, extensions, and manual work. Sources: [squarespace-ai], [squarespace-plans] |
| Production meter | Price one site plan plus relevant payment-processing or transaction fees, domains, email, scheduling, digital products, extensions, and provider services. Plan and country availability require account-level verification. Sources: [squarespace-plans], [squarespace-fees], [squarespace-integrations] |
Tradeoffs
- A cohesive visual system simplifies many content-led sites while asking bespoke behavior to fit supported blocks, code paths, integrations, or external services.
- Commerce, digital products, payment processing, scheduling, email, domains, and extensions can have separate fees or subscriptions.
- WordPress XML and product CSV exports do not reproduce the complete design, store, style, media, and service state.
Webflow
Best for: A team that needs a structured CMS, visual design controls, role-aware publishing, client handoff, or a bounded static-code export path.
Webflow separates the hosted Site plan from the Workspace used to build and collaborate. Its static code export is useful but excludes CMS content and hosted functionality.
| Criterion | Finding |
|---|---|
| Authoring model | Webflow documents a visual Designer with reusable classes, components, variables, CMS templates, interactions, and role-aware site editing. Sources: [webflow-intro], [webflow-roles] |
| Website output | A paid Site plan provides managed Webflow hosting and a custom domain. A paid Workspace can export bounded static site files, but hosted CMS and application features do not travel with that archive. Sources: [webflow-pricing], [webflow-export] |
| Content and SEO | Webflow CMS uses collection schemas, items, fields, URLs, and generated collection pages. Plan limits determine the available content scale and publishing features. Sources: [webflow-cms], [webflow-pricing] |
| Business workflows | Webflow can host site and CMS behavior, while apps and external services add separate permissions, data, pricing, and migration boundaries. Validate forms, ecommerce, members, and providers individually. Sources: [webflow-pricing], [webflow-apps] |
| Domain and publishing | A paid Site plan connects a custom domain and managed hosting. Workspace roles can separate design, content, review, and publishing access. Sources: [webflow-pricing], [webflow-roles] |
| Ownership and export | Static code export includes documented files but excludes CMS content and functionality, user accounts, ecommerce, forms, search, code components, and localized content. Those need separate exports or replacements. Sources: [webflow-export] |
| Recovery boundary | Webflow documents automatic and manual restore points with plan and permission boundaries. Restore can affect CMS, ecommerce, scheduled items, locales, comments, and settings, so rehearse on the actual site. Sources: [webflow-backups] |
| Collaboration and handoff | Site roles separate managers, designers, marketers, content editors, reviewers, publishing, and backup access. A client handoff must also assign Workspace, Site plan, billing, domain, apps, and exported assets. Sources: [webflow-roles], [webflow-pricing] |
| Build meter | Workspace plans and seats govern collaboration and code export, and current pricing includes plan-specific AI credits. Record Site and Workspace layers, seats, AI use, add-ons, and manual interventions. Sources: [webflow-pricing] |
| Production meter | Price the Site plan, Workspace plan where needed, seats, bandwidth, CMS scale, add-ons, apps, domains, and external providers. Site hosting and team authoring are separate purchase layers. Sources: [webflow-pricing], [webflow-apps] |
Tradeoffs
- Separate Site and Workspace plans make hosting and collaboration explicit while making total cost harder to infer from one headline price.
- Static code export excludes CMS content and functionality, ecommerce, forms, search, localized content, and other hosted features.
- Backups can restore site and CMS state inside Webflow, while external runtime, provider, domain, and data recovery remain separate.
Wix
Best for: A team that wants AI-assisted or visual site creation, managed Wix hosting, packaged business features, and an app ecosystem under site-level plan limits.
Wix combines site creation, editing, hosting, business plans, CMS, payments, apps, history, and site transfer inside a managed platform. The runnable site remains on Wix infrastructure.
| Criterion | Finding |
|---|---|
| Authoring model | Wix documents an AI Website Builder that gathers requirements in chat, creates a new site design, and hands the result to the Wix Editor. Existing-site redesign uses separate editor tools. Sources: [wix-ai] |
| Website output | Wix includes hosting for its sites and states that a Wix-built site depends on its SaaS services and must be hosted and operated on Wix servers rather than exported as a runnable site elsewhere. Sources: [wix-hosting], [wix-export] |
| Content and SEO | Wix Studio documents CMS collections and dynamic content. Plan choice controls storage, collaborators, forms, and business features; verify metadata, redirects, URLs, collection permissions, and editorial roles on the exact site. Sources: [wix-cms], [wix-plan-features] |
| Business workflows | Payment acceptance requires an eligible plan and depends on regional providers. Wix-built and third-party apps add separate permissions, billing, support, data, and migration boundaries. Sources: [wix-payments], [wix-apps], [wix-plan-features] |
| Domain and publishing | Wix includes site hosting and requires an eligible paid plan for a connected custom domain. Domain registration, mailboxes, apps, payments, and other subscriptions can renew separately. Sources: [wix-hosting], [wix-plan-pricing] |
| Ownership and export | Wix says site content belongs to the customer while the runnable site stays on Wix infrastructure. Physical store products have a bounded CSV export; other content and data classes need separate checks. Sources: [wix-export], [wix-product-export] |
| Recovery boundary | Wix documents site history and restoring saved versions inside the platform. That editor recovery does not create an externally hosted site archive or automatically restore domains, apps, payments, and provider data. Sources: [wix-history], [wix-export] |
| Collaboration and handoff | A Wix site can transfer to another Wix account, with the recipient accepting ownership and future billing. Wix Payments does not follow the same transfer path, so website and payment-account handoff stay separate. Sources: [wix-transfer] |
| Build meter | One Premium plan applies to one site, while collaborators, AI tools, apps, and manual implementation can add other constraints. Record the exact editor, site plan, apps, and interventions used for the brief. Sources: [wix-plan-pricing], [wix-plan-features] |
| Production meter | Price the regional site plan plus storage, collaborators, forms, payment acceptance, ecommerce, domains, mailboxes, apps, and providers. Wix states that public pricing varies by geographic location. Sources: [wix-plan-pricing], [wix-plan-features], [wix-apps] |
Tradeoffs
- The managed platform reduces separate hosting work while keeping the runnable Wix site on Wix servers.
- A broad app and business-feature ecosystem can shorten setup while adding plan, provider, data, billing, and migration dependencies.
- Site transfer and content ownership do not make every payment account, domain, mailbox, app, product type, or hosted implementation portable.
WordPress.com
Best for: A team that wants managed WordPress hosting and publishing, then accepts the selected plan, theme, plugin, maintenance, and export boundary.
WordPress.com packages WordPress software with managed hosting, plans, updates, backups, themes, plugins, and support. It must be distinguished from a separately hosted WordPress.org installation.
| Criterion | Finding |
|---|---|
| Authoring model | WordPress.com uses the WordPress CMS, content editor, media, themes, and plan-dependent plugins inside managed hosting. Do not mix this track with a separately hosted WordPress.org installation. Sources: [wordpress-com-vs-org], [wordpress-com-plan-features] |
| Website output | The documented output is a managed WordPress.com site. WordPress.org uses the same software family but requires a separately chosen host and different operational responsibility. Sources: [wordpress-com-vs-org] |
| Content and SEO | WordPress.com provides the WordPress content model and plan-dependent website features. The selected theme and plugins shape the exact authoring, metadata, redirect, schema, and editorial workflow. Sources: [wordpress-com-plan-features], [wordpress-com-plugins] |
| Business workflows | Paid plans document plugin installation, including third-party and paid plugin paths. Every active plugin adds its own publisher, license, permissions, updates, data, support, and replacement boundary. Sources: [wordpress-com-plugins], [wordpress-com-pricing] |
| Domain and publishing | WordPress.com plans package managed hosting and plan-dependent site features. Confirm domain inclusion and renewal, storage, support, traffic, email, and any external service in the current checkout. Sources: [wordpress-com-pricing], [wordpress-com-plan-features] |
| Ownership and export | The standard export creates XML for posts, pages, and comments, with media references handled separately. It excludes the theme design, customizations, and plugins, so it is not a complete site copy. Sources: [wordpress-com-export] |
| Recovery boundary | WordPress.com says it creates automatic backups, and its current export guide points Business and Commerce plans to full-backup download and restore paths. Confirm plan eligibility, retention, restore permissions, theme and plugin state, domain, and external-provider recovery. Sources: [wordpress-com-export], [wordpress-com-plan-features] |
| Collaboration and handoff | A handoff must inventory the WordPress.com account, site roles, plan, billing, domain, plugins, premium licenses, media, exported content, and external providers. Content export alone does not transfer those controls. Sources: [wordpress-com-export], [wordpress-com-plugins] |
| Build meter | Record the plan, paid theme or plugins, implementation time, imports, and manual edits. The reviewed sources do not define one universal AI-generation meter comparable with prompt-led builders. Sources: [wordpress-com-pricing], [wordpress-com-plugins] |
| Production meter | Price the current plan, storage and feature limits, domain and email renewals, premium themes or plugins, external providers, support, and operator time rather than treating WordPress software as the whole cost. Sources: [wordpress-com-pricing], [wordpress-com-plan-features], [wordpress-com-plugins] |
Tradeoffs
- Managed hosting reduces server and update work while introducing WordPress.com plan and service boundaries.
- Themes and plugins expand the site while adding publishers, licenses, permissions, updates, data, support, and replacement dependencies.
- The standard content export does not include theme design, customizations, plugins, or a complete media archive.
Decision rules for the shortlist
Choose the smallest operating boundary that meets the real site job and that the long-term owner can understand, pay for, recover, and transfer.
The site is one focused page with a simple form or link destination
Choose: Evaluate Carrd first, then test the exact form, domain, export, transfer, and recovery requirements before selecting a Pro tier.
Tradeoff: The one-page boundary is economical only while a real multi-page CMS, store, login, or durable workflow is not required.
Visual design, structured content, and controlled publishing are central
Choose: Compare Framer and Webflow on the frozen brief, with the required CMS scale, roles, staging, export, bandwidth, and handoff owner.
Tradeoff: The richer production workflow adds plan, seat, bandwidth, CMS, and platform-dependency decisions.
The team wants a managed general-purpose business website
Choose: Compare Wix and Squarespace on the exact pages, contributors, forms, commerce, integrations, export classes, and ownership handoff.
Tradeoff: Packaged site tools reduce infrastructure work while keeping more of the runnable site inside the provider boundary.
Products, checkout, orders, fulfillment, and apps define the business
Choose: Evaluate Shopify as the commerce operating system and include transaction, payment, app, theme, domain, fulfillment, and transfer work.
Tradeoff: Commerce depth is useful for a store and unnecessary complexity for a simple informational site.
Managed WordPress publishing and plugin compatibility are requirements
Choose: Evaluate WordPress.com as a named managed track, then verify the plan, theme, plugins, export, backup, domain, and handoff boundary.
Tradeoff: Plugins broaden capability while multiplying supplier, permission, update, support, and recovery dependencies.
The site may become a custom portal, dashboard, database, or workflow
Choose: Evaluate Playcode on the same bounded website brief and the first required application slice, keeping project code, live data, providers, and recovery separate.
Tradeoff: The custom path can grow beyond a fixed site model while asking the team to review generated behavior and track AI plus production meters.
Any run lacks an acceptance result or required output SHA-256
Choose: Mark the run incomplete and do not score it. Preserve the source set, failed checks, manual interventions, and meter evidence for a clean rerun.
Tradeoff: The decision takes longer, but incomplete evidence is safer than a winner inferred from a demo or price card.
TEST THE SAME BRIEF
Build a no-code website with Playcode
Describe the pages, content, form states, domain, and handoff you need. Refine the result visually or by chat, then verify the exact publishing, export, provider, and recovery boundary before release.
Build a no-code websitePlaycode is not scored in this guide. Use the same frozen brief and acceptance record.
Check current Playcode plans and limits.Record current terms when reproducing the benchmark.
Evidence and benchmark limits
This page is a dated first-party documentation review plus a reproducible benchmark protocol. It is not a completed hands-on benchmark, performance test, security review, or procurement approval.
- No identical website was built, timed, accessibility-tested, published, migrated, or restored in all nine products for this article; every platform output hash is intentionally null.
- The three visible SHA-256 values lock the brief, acceptance manifest, and output contract, not a product-generated site.
- Plan names, regional prices, promotional terms, renewals, AI units, usage limits, transaction fees, app terms, storage, bandwidth, and collaboration rules can change before the August 31 review date.
- First-party documentation supports product-boundary facts but cannot prove ease of use, design quality, speed, uptime, support quality, conversion, accessibility, security, or reliability.
- A project-code or static-site download does not prove content, database, submissions, media, secrets, domains, accounts, payments, apps, or provider settings can move with it.
- A platform version or backup does not automatically prove complete production recovery; scope, retention, permissions, external dependencies, and a rehearsal still matter.
- Playcode publishes this guide and is one of the compared products. Its placement first is a disclosure choice, not a ranking signal.
Official sources checked in July and August 2026
Every material product finding cites a first-party page. Access dates show when this review used the source, not when an undated provider page was revised. Recheck volatile facts by August 31, 2026.
[playcode-builder] Playcode:No-Code Website Builder
Checked August 1, 2026. Supports: Plain-language website creation, visual and chat iteration, publishing, and the custom website workflow.
[playcode-cloud] Playcode:Playcode Cloud
Checked August 1, 2026. Supports: Backend, database, files, HTTPS, domains, jobs, WebSockets, previews, snapshots, rollback, and runtime boundaries.
[playcode-pricing] Playcode:Playcode Pricing
Checked August 1, 2026. Supports: Current plan, AI-credit, Cloud-app, collaboration, domain, hosting, and project-code export boundaries.
[carrd-overview] Carrd:Carrd Product and Builder Overview
Checked July 19, 2026. Supports: One-page scope, template or blank start, canvas arrangement, properties, preview, and publishing.
[carrd-plans] Carrd:Carrd Pro Plans
Checked July 19, 2026. Supports: Plan prices, site slots, domains, forms, widgets, sharing, transfers, and download gates.
[carrd-sections] Carrd:Using Sections
Checked July 19, 2026. Supports: Named sections that simulate multiple pages within a one-page Carrd site.
[carrd-domain] Carrd:Using a Custom Domain
Checked July 19, 2026. Supports: Custom-domain publishing, DNS setup, forwarding, and SSL.
[carrd-forms] Carrd:Setting Up a Custom Form
Checked July 19, 2026. Supports: Plan-gated form destinations, email, URLs, automation tools, and custom code.
[carrd-transfer] Carrd:Sharing and Transferring Sites
Checked July 19, 2026. Supports: Site ownership transfer to an eligible Carrd account and account prerequisites.
[carrd-download] Carrd:Downloading a Site
Checked July 19, 2026. Supports: Pro Plus source download, Carrd-dependent form failure outside the platform, and no re-import boundary.
[framer-pricing] Framer:Framer Pricing
Checked August 1, 2026. Supports: Current site plans, pages, CMS, bandwidth, AI credits, editor roles, site limits, and add-ons.
[framer-bandwidth] Framer Help:Understanding Bandwidth Usage
Checked August 1, 2026. Supports: Monthly bandwidth measurement, notifications, upgrades, and overage handling.
[framer-export] Framer Help:Can I Export My Website to HTML and Self-Host It?
Checked August 1, 2026. Supports: No standalone HTML export and dependencies on Framer rendering, optimization, caching, and hosting.
[framer-staging] Framer Help:Staging and Versions
Checked August 1, 2026. Supports: Version links, custom-domain staging, deployment, published versions, and rollback.
[framer-version-history] Framer Help:Revert to a Previous Working Version
Checked August 1, 2026. Supports: View-only snapshots, history cadence, and copying earlier content into the canvas.
[framer-roles] Framer Help:Members, Roles, and Permissions
Checked August 1, 2026. Supports: Workspace, project, design, content, deploy, editor, viewer, and billing roles.
[framer-transfer] Framer Help:Transfer a Project to Another User
Checked August 1, 2026. Supports: Transfer authority, domain continuity, subscription cancellation, and recipient plan choice.
[hostinger-plans] Hostinger:Hostinger Plans and Website Builder
Checked August 1, 2026. Supports: Current promotional and renewal terms, site counts, domain term, storage, backups, builder, ecommerce, email, and AI-tool packaging.
[hostinger-backups] Hostinger Help Center:Create and Restore Website Builder Backups
Checked August 1, 2026. Supports: Published-site backup creation, update versions, retention, preview, and editor restore.
[hostinger-export] Hostinger Help Center:Export Website Builder Content to WordPress
Checked August 1, 2026. Supports: WordPress content-export prerequisites, supported pages and media, and excluded layout, store, forms, submissions, integrations, and SEO settings.
[shopify-online-store] Shopify Help Center:Online Store
Checked August 1, 2026. Supports: Hosted store pages, blog, themes, navigation, search, custom domains, checkout, and custom storefront boundary.
[shopify-themes] Shopify Help Center:Shopify Themes
Checked August 1, 2026. Supports: Theme selection, customization, licensing, support, publication, and management.
[shopify-products] Shopify Help Center:Products
Checked August 1, 2026. Supports: Catalog, variants, media, inventory, tags, metafields, collections, and bulk work.
[shopify-pricing] Shopify Help Center:Pricing Plans
Checked August 1, 2026. Supports: Plan selection, upgrades, local pricing, POS consideration, and account verification.
[shopify-apps] Shopify Help Center:Managing Apps
Checked August 1, 2026. Supports: App billing, usage charges, permissions, privacy, compatibility, history, and support.
[shopify-product-export] Shopify Help Center:Exporting Products
Checked August 1, 2026. Supports: Product CSV export, backup and migration use, variants, images, and inventory boundaries.
[shopify-transfer] Shopify Help Center:Change or Transfer Ownership
Checked August 1, 2026. Supports: Store transfer plus contact, domain, billing, app, payout, tax, payment-provider, and permission checklist.
[shopify-theme-copy] Shopify Help Center:Duplicating Themes
Checked August 1, 2026. Supports: Theme duplication before customization and the theme-only recovery boundary.
[squarespace-ai] Squarespace Help Center:Using Squarespace AI
Checked August 1, 2026. Supports: Blueprint AI, AI templates, generated content, and owner review responsibility.
[squarespace-fluid-engine] Squarespace Help Center:Edit Your Site with Fluid Engine
Checked August 1, 2026. Supports: Version 7.1 block-section drag-and-drop editing and its version boundary.
[squarespace-plans] Squarespace Help Center:Choosing the Right Squarespace Plan
Checked August 1, 2026. Supports: Current plan framing, contributors, code, commerce, video, and fee boundaries.
[squarespace-hosting] Squarespace Help Center:Is Hosting Included?
Checked August 1, 2026. Supports: Included hosting and bandwidth plus the external-platform hosting boundary.
[squarespace-fees] Squarespace Help Center:Transaction Fees and Payment Processing Rates
Checked August 1, 2026. Supports: Plan, country, processor, commerce, digital-product, invoice, and scheduling fees.
[squarespace-integrations] Squarespace Help Center:Squarespace Integrations
Checked August 1, 2026. Supports: Official integrations, separate subscriptions, extensions, and custom-code paths.
[squarespace-ownership] Squarespace Help Center:Change the Site Owner
Checked August 1, 2026. Supports: Owner transfer, contributor prerequisite, subscriptions, payment follow-up, and access review.
[squarespace-export] Squarespace Help Center:Exporting Your Site
Checked August 1, 2026. Supports: WordPress XML export plus supported and excluded content classes.
[squarespace-product-export] Squarespace Help Center:Exporting Products to a CSV
Checked August 1, 2026. Supports: Separate product CSV export and its distinction from the partial site export.
[webflow-pricing] Webflow:Webflow Plans and Pricing
Checked August 1, 2026. Supports: Site and Workspace plans, CMS, bandwidth, AI credits, code export, roles, and add-ons.
[webflow-intro] Webflow Help Center:Introduction to Webflow
Checked August 1, 2026. Supports: Visual Designer, classes, components, variables, CMS, interactions, and publishing.
[webflow-cms] Webflow Help Center:Manage CMS Collections
Checked August 1, 2026. Supports: Collection schemas, items, fields, URLs, and generated collection pages.
[webflow-apps] Webflow Help Center:Webflow Apps Overview
Checked August 1, 2026. Supports: App installation, permissions, publisher, data, billing, support, and removal boundaries.
[webflow-export] Webflow Help Center:Export Webflow Site Code
Checked August 1, 2026. Supports: Paid-Workspace static export, included files, and excluded hosted features.
[webflow-backups] Webflow Help Center:Save and Restore Backups
Checked August 1, 2026. Supports: Automatic and manual restore points, permissions, CMS, ecommerce, locale, and settings effects.
[webflow-roles] Webflow Help Center:Site Roles and Permissions
Checked August 1, 2026. Supports: Site manager, designer, marketer, content editor, reviewer, publish, and backup access.
[wix-ai] Wix Help Center:Creating an AI-Generated Site
Checked August 1, 2026. Supports: AI requirement chat, new-site generation, Editor handoff, and existing-site boundary.
[wix-plan-pricing] Wix Help Center:Wix Premium Plan Pricing
Checked August 1, 2026. Supports: Regional variation, one plan per site, custom-domain requirement, and plan changes.
[wix-plan-features] Wix Help Center:Choosing a Premium Plan
Checked August 1, 2026. Supports: Storage, collaborators, forms, payments, ecommerce, and business-feature boundaries.
[wix-hosting] Wix Help Center:Wix Site Hosting
Checked August 1, 2026. Supports: Included hosting, free-site limits, and custom-domain paid-plan requirement.
[wix-cms] Wix Help Center:Using the Wix Studio CMS
Checked August 1, 2026. Supports: Collections, dynamic content, dataset connections, and Wix Studio CMS workflow.
[wix-payments] Wix Help Center:Accepting Payments Overview
Checked August 1, 2026. Supports: Eligible plans, regional payment providers, methods, setup, and account boundaries.
[wix-apps] Wix Help Center:Adding an App to Your Site
Checked August 1, 2026. Supports: Wix and third-party apps, plans, permissions, services, and installation.
[wix-export] Wix Help Center:Exporting or Embedding Your Wix Site Elsewhere
Checked August 1, 2026. Supports: Content ownership, Wix-hosted operation, external-hosting boundary, and domains.
[wix-product-export] Wix Help Center:Exporting Your Product List
Checked August 1, 2026. Supports: Physical-product CSV export, row limits, and digital-product exclusion.
[wix-transfer] Wix Help Center:Accepting Transferred Site Ownership
Checked August 1, 2026. Supports: Ownership acceptance, Premium billing handoff, media access, and Wix Payments exclusion.
[wix-history] Wix Help Center:Viewing, Managing, and Restoring Site History
Checked August 1, 2026. Supports: Saved site versions, history access, preview, restore, and platform recovery boundary.
[wordpress-com-vs-org] WordPress.com Support:WordPress.com vs. WordPress.org
Checked August 1, 2026. Supports: Managed hosting, self-hosting distinction, updates, backups, plugins, and responsibility.
[wordpress-com-pricing] WordPress.com:WordPress.com Pricing
Checked August 1, 2026. Supports: Current public plan structure, hosting, storage, support, and features.
[wordpress-com-plan-features] WordPress.com Support:WordPress.com Plan Features
Checked August 1, 2026. Supports: Plan-dependent hosting, design, content, storage, support, and website features.
[wordpress-com-plugins] WordPress.com Support:WordPress.com Plugins
Checked August 1, 2026. Supports: Plugin installation, paid plugins, third-party publishers, and plan boundaries.
[wordpress-com-export] WordPress.com Support:Export Your Website Content
Checked August 1, 2026. Supports: XML content export, included content, excluded design and plugins, media handling, and the plan-gated full-backup download and restore boundary.
No-code website builder FAQ
Which no-code website builder is best?
There is no universal winner. Carrd fits a focused one-page site; Framer and Webflow fit design-led production; Wix and Squarespace fit managed general-purpose sites; Shopify fits commerce-first operations; WordPress.com fits managed WordPress publishing; Hostinger packages a builder with hosting; and Playcode fits a prompt-led custom site that may grow into application workflows.
Did Playcode test all nine website builders?
No. This page reviews current first-party documentation and freezes benchmark service-business-website-v1 with ten acceptance tests and three contract hashes. It does not report a completed nine-product run. Every platform output SHA-256 remains empty, so the article names no hands-on benchmark winner.
Can I export a no-code website?
Export is not one yes-or-no field. Webflow documents a bounded static export, Carrd a plan-gated download, Playcode a project-code export, and several hosted builders partial content or product exports. Test code, content, media, submissions, live records, domains, accounts, secrets, apps, payments, and provider settings separately.
Which no-code website builder is best for a one-page site?
Carrd is a documented one-page specialist and can use sections to simulate multiple views. Framer, Webflow, Wix, Squarespace, Hostinger, WordPress.com, Shopify, and Playcode can also produce focused pages, but their wider plans and operating boundaries may be unnecessary when one page and one simple handoff are the whole job.
Which no-code website builder is best for an online store?
Evaluate Shopify when products, inventory, checkout, orders, fulfillment, and apps define the business. Wix and Squarespace also document commerce paths, while Hostinger packages ecommerce in current plans. Compare payment availability, transaction and provider fees, catalog export, app dependencies, ownership transfer, and recovery before choosing.
Which no-code website builder gives me the most ownership?
Ownership must be decomposed. Record project code, static files, content, products, media, submissions, database records, domains, accounts, secrets, apps, payments, and provider configuration. A code download can be valuable without moving live data; a site transfer can change billing ownership without producing an independently runnable copy.
How should I compare no-code website builder prices?
Use the current region, plan, billing term, promotion and renewal, then add sites, pages, CMS records, storage, bandwidth, collaborators, AI use, apps, transactions, domains, email, external providers, support, and operator work. Starting price alone does not describe the first production month or the later renewal month.
What should I test before publishing?
Use one fixed brief and test cold publication, responsive layout, navigation and canonical URLs, independent content edits, invalid and successful form states, search metadata, keyboard access, export boundaries, recovery, and every build and production meter. Keep hashes and failed attempts so a later run is comparable.
KEEP THE EVIDENCE
Choose the boundary you can operate and recover
Start with the smallest site job that proves content editing, one real handoff, publishing, export, and recovery. Keep every meter and output in the same review record.
Start with PlaycodeKeep code, content, live data, domains, accounts, and providers as separate checks.