QUICK ANSWER
What are the best landing page builders in 2026?
There is no universal winner. Shortlist Carrd for simple low-cost pages, HubSpot for CRM-connected campaigns, Instapage or Unbounce for paid acquisition, Landingi for campaign operations, Leadpages for built-in CRO without traffic caps, Webflow for design-led sites, or Playcode when a page must become custom software. Pilot every required boundary before choosing.
The best landing page builder is not the one with the longest feature list. It is the one that can publish your real campaign, deliver a valid lead, measure the intended event, support the people who operate it, and leave you an acceptable exit path at the traffic level you expect.
We reviewed dated first-party product, help, pricing, permissions, and export documentation on August 1, 2026. This is an unordered documentation comparison, not a controlled eight-provider benchmark. Playcode publishes the guide and appears as a disclosed custom page-to-app path. We use no affiliate links, receive no referral compensation, and assign no universal winner.
Use required gates, not a total score
Freeze one campaign, classify each boundary as required, preferred, or irrelevant, and convert every unknown or not-reproduced requirement into a pilot test. A documented capability is a research lead, not acceptance evidence.
Freeze one representative campaign brief
Use the same custom domain, responsive page, consent-bearing form, invalid and duplicate submissions, thank-you state, CRM or webhook destination, UTM events, variant, two user roles, SEO fields, lead export, page export, republish, and recovery case for every finalist.
Sources: [unbounce-features], [instapage-plans], [leadpages-getting-started]
Classify every criterion before reviewing brands
Mark each of the eight rows required, preferred, or irrelevant. An explicit limitation that misses a required need removes an option for this brief. An unknown or untested requirement means pilot required, not pass or fail.
Sources: [carrd-plans], [hubspot-content-pricing], [landingi-pricing], [webflow-pricing]
Review the same first-party source types
For each provider, check current pricing plus publishing, forms, experimentation, permissions, SEO, and export documentation. Preserve conflicts between official pages instead of choosing the convenient value.
Sources: [carrd-export], [hubspot-export], [instapage-export], [landingi-export], [leadpages-terms], [playcode-cloud], [unbounce-export], [webflow-export]
Run the production-shaped pilot
Use the named plan and frozen fixture. Record procedure, expected and observed results, timestamps, exported files, network or delivery evidence, and failures. Vendor demos, help examples, and conversion claims do not count as reproduction.
Sources: [hubspot-ab], [instapage-leads], [landingi-integrations], [leadpages-ab]
Price the complete operating month and exit
Capture the current checkout or quote, then count traffic, pages, domains, seats, contacts, storage, credits, add-ons, integrations, overages, implementation, monitoring, and operator time. Export the page and lead data before approving the exit boundary.
Sources: [carrd-plans], [hubspot-content-pricing], [instapage-plans], [landingi-pricing], [leadpages-pricing], [playcode-pricing], [unbounce-pricing], [webflow-pricing]
What this landing page builder guide owns
This page owns general campaign and conversion-operations platform selection. It compares the whole path from editing through publishing, lead delivery, experimentation, governance, cost, and exit.
Included
- Eight unordered options covering dedicated campaign platforms, a lightweight one-page tool, a CRM-connected suite, a design-led site platform, and a disclosed custom page-to-app path.
- The same eight publishing, editor, form, analytics, testing, integration, performance, SEO, collaboration, export, ownership, pricing, traffic, and usage boundaries for every option.
- Dated first-party sources, explicit conflicts and unknowns, a buyer-owned pilot contract, and a deterministic evidence pack.
Not included
- AI-only landing page builder selection, which is a separate existing article with AI generation as the selection universe.
- Transactional create-or-build intent, which belongs to the commercial landing-page product owners rather than this editorial guide.
- A general best website builder list, a provider-versus-provider page, an SEO-platform ranking, or a conversion-rate tutorial.
- Hands-on speed, accessibility, deliverability, uptime, support, security, experiment, or conversion results that the not-run pilot has not reproduced.
- An exhaustive directory. Omitted tools can still be the correct fit for a buyer outside the frozen campaign brief.
Eight criteria that expose the real operating model
Source-reviewed means an official page supports the narrow statement. Partially reviewed means a boundary remains. Source conflict preserves incompatible official statements. Unknown means the reviewed official pages did not establish the behavior. Every cell is also marked not reproduced.
Page publishing and domain
Hosted previews, custom roots or subdomains, HTTPS, staging, republishing, and subscription dependencies determine whether a campaign can go live on the intended address.
Templates, editor, and design control
A template count is inventory, not quality. The real boundary is whether the team can reproduce its brand, responsive states, reusable sections, custom code, and review workflow.
Forms and lead delivery
Fields, validation, consent, spam handling, success states, retention, notifications, export, and CRM or webhook delivery are separate parts of one lead path.
Analytics, testing, and integration boundaries
Pageviews, events, attribution, randomized variants, traffic allocation, statistical decisions, CRM delivery, and external pixels are different capabilities with different plan gates.
Performance and SEO controls
Managed hosting does not prove a fast or search-ready result. Inspect metadata, canonical, indexation, sitemap, robots, redirects, schema, images, scripts, and the published output.
Collaboration and governance
Seats, roles, comments, approvals, workspaces, reusable blocks, staging, history, audit logs, and publish permissions control how safely a team can operate pages.
Export and ownership
Customer ownership, project transfer, static source, form data, analytics, integrations, experiments, accounts, and a complete runnable export are different exit surfaces.
Current pricing, traffic, and usage meters
The useful cost is the lowest plan that fits the reference campaign after traffic, pages, domains, seats, storage, credits, contacts, integrations, add-ons, and overages.
Eight landing page builders, presented alphabetically
Alphabetical order prevents the roster from implying a rank. Playcode is included as the disclosed publisher path. The findings describe conditional fit, not endorsements, scores, ratings, or a universal recommendation.
Carrd
Best for: A focused, low-cost, mostly one-page campaign that needs a custom domain and a straightforward form.
Carrd is a responsive one-page builder with a low annual production price. Higher Pro tiers add advanced forms, SEO controls, collaboration, and static-source download, while native experimentation remains undocumented.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Pro Standard and higher support custom roots or subdomains with managed Let's Encrypt SSL; the free tier publishes on Carrd subdomains. Sources: [carrd-domain], [carrd-plans] |
| Templates, editor, and design control | Partially source-reviewed, not reproduced: Templates or a blank canvas, responsive one-page output, sections, appearance controls, mobile preview, and undo or redo are documented; template count does not prove design quality. Sources: [carrd-building] |
| Forms and lead delivery | Source-reviewed, not reproduced: Pro Standard contact and signup forms can email recipients or connect supported services; Pro Plus adds custom delivery to automation tools, arbitrary URLs, and checkout paths. Delivery was not tested. Sources: [carrd-forms], [carrd-plans] |
| Analytics, testing, and integration boundaries | Unknown - not documented, not reproduced: External analytics, trackers, embeds, and widgets are documented, but the reviewed first-party pages did not establish native randomized A/B testing, statistical confidence, or winner selection. Not tested. Sources: [carrd-analytics], [carrd-plans] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Responsive hosting and automatic sitemaps are documented; Pro Standard adds meta tags, while Pro Plus adds canonical URLs, custom robots or site files, redirects, and cache update frequency. Published performance was not measured. Sources: [carrd-seo], [carrd-plans] |
| Collaboration and governance | Partially source-reviewed, not reproduced: Shared access supports Admin, Editor, and Template permissions and site ownership transfer. The reviewed sources did not establish approvals, audit logs, or version-history governance. Sources: [carrd-sharing] |
| Export and ownership | Source-reviewed, not reproduced: Pro Plus can download unminified HTML, CSS, JavaScript, and assets. Carrd-dependent features such as forms do not work after export, and the archive cannot be imported back. Sources: [carrd-export] |
| Current pricing, traffic, and usage meters | Source-reviewed, not reproduced: Pro Standard is USD 19 per year for 10 sites with custom domains, forms, analytics, embeds, and meta tags. Pro Plus is USD 49 per year for 25 sites plus advanced forms, SEO controls, and source download. No native traffic meter was documented. Sources: [carrd-plans] |
Tradeoffs
- Its one-page model is intentionally narrower than a campaign operations suite or broader site platform.
- Advanced forms, canonical controls, redirects, and source download require Pro Plus rather than the entry campaign tier.
- Downloaded source does not preserve Carrd-dependent form behavior and cannot be imported back into Carrd.
HubSpot
Best for: Teams that want landing pages, forms, contacts, campaign reporting, and permissions inside one CRM-connected content system.
HubSpot combines page publishing with forms, CRM records, reporting, templates, and granular permissions. Meaningful experimentation, page scale, marketing-contact billing, and governance depend on the selected Hub and tier.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Free accounts can use a HubSpot-branded domain; connected custom domains require DNS access and the applicable publishing permissions and subscription boundary. Sources: [hubspot-pages], [hubspot-domain] |
| Templates, editor, and design control | Source-reviewed, not reproduced: Theme and custom templates, drag-and-drop areas, reusable modules, page settings, and custom code paths are documented. A configured template and responsive result still need review. Sources: [hubspot-pages] |
| Forms and lead delivery | Source-reviewed, not reproduced: Pages can use forms and meeting links, and captured contacts enter HubSpot CRM workflows according to account configuration. Consent, deduplication, routing, notifications, and downstream delivery were not reproduced. Sources: [hubspot-landing-pages] |
| Analytics, testing, and integration boundaries | Source-reviewed, not reproduced: Page performance reporting and same-URL A/B tests are documented; current help gates page A/B testing to Content Hub Professional or Enterprise. Integrations and automation remain separate configured surfaces. Sources: [hubspot-ab], [hubspot-analytics] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Page title, URL, meta description, canonical, stylesheets, header or footer code, and SEO recommendations are documented. Vendor uptime and performance claims were not independently measured. Sources: [hubspot-pages] |
| Collaboration and governance | Source-reviewed, not reproduced: HubSpot documents separate view, edit, publish, private-content, domain, and user-management permissions. Exact role availability depends on the subscription and assigned seat. Sources: [hubspot-permissions] |
| Export and ownership | Partially source-reviewed, not reproduced: Pages, posts, templates, and content data can be exported as documented formats including HTML. CRM state, workflows, tests, reports, permissions, and connected services require separate export or rebuild checks. Sources: [hubspot-export] |
| Current pricing, traffic, and usage meters | Source conflict, not reproduced: Content Hub currently shows Free, a Starter promotion from USD 7 per seat per month versus USD 20 standard, Professional from USD 450 with annual commitment or USD 500 monthly, and Enterprise from USD 1,500. Page limits, seats, credits, and marketing contacts are separate meters; confirm the live quote. Sources: [hubspot-content-pricing], [hubspot-pages] |
Tradeoffs
- Landing-page price cannot be separated cleanly from the selected Content or Marketing Hub, seats, contacts, credits, and add-ons.
- A/B testing is documented for Professional and Enterprise, not Free or Starter.
- HTML and content exports do not automatically reproduce CRM records, automation, reports, permissions, or connected integrations.
Instapage
Best for: Paid acquisition teams that need precise visual construction, reusable blocks, review comments, and plan-gated server-side experimentation.
Instapage is a hosted campaign platform with visual editing, forms, collaboration, analytics, and paid-tier experimentation. Its customer-content ownership does not provide a deployable HTML export.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Partially source-reviewed, not reproduced: Custom subdomain, WordPress, Drupal, test-domain, and SSL publishing are documented. Current pricing places explicit root-domain publishing on Convert, so verify the exact domain shape and plan. Sources: [instapage-publishing], [instapage-plans] |
| Templates, editor, and design control | Source conflict, not reproduced: Current pricing documents 200+ responsive templates, canvas and fluid-grid controls, grouping, mobile editing, reusable blocks, and custom code. Other official pages publish different template counts. Sources: [instapage-plans] |
| Forms and lead delivery | Source-reviewed, not reproduced: Reusable forms, stored contacts, email, lead export, and notification recipients are documented. Optimize adds multi-step forms and Convert adds direct lead bypass. Delivery and retention were not reproduced. Sources: [instapage-leads], [instapage-plans] |
| Analytics, testing, and integration boundaries | Source-reviewed, not reproduced: Built-in visits, conversions, bounce rate, and conversion rate are documented. Optimize adds server-side A/B testing; Convert adds heatmaps and AI experiments. The 120+ integration catalog mixes native, Zapier, and external-app paths. Sources: [instapage-analytics], [instapage-integrations], [instapage-plans] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Hosted rendering, SSL, image optimization, metadata, canonical URL, indexation, JSON-LD, and domain sitemaps are documented. Instapage says it cannot generate robots.txt; speed was not benchmarked. Sources: [instapage-seo] |
| Collaboration and governance | Source conflict, not reproduced: Comments, annotations, Viewer, Editor, and Manager permissions are documented. Marketing language says real-time edits, while help documentation says only one active person can edit a page at once. Audit logs and SSO are higher-tier. Sources: [instapage-team], [instapage-plans] |
| Export and ownership | Source-reviewed, not reproduced: Customers own their content, but page export is a proprietary Instapage file rather than HTML. Re-upload omits integrations, scripts, privacy, SEO or social settings, and global blocks; hosting remains subscription-dependent. Sources: [instapage-export] |
| Current pricing, traffic, and usage meters | Source conflict, not reproduced: Create is USD 99 monthly or USD 79 annual-effective with 15,000 monthly visitors. Optimize is USD 199 or USD 159 with 30,000 visitors. Live pricing says unlimited pages, while usage documentation still describes plan limits; confirm the account screen. Sources: [instapage-plans], [instapage-usage] |
Tradeoffs
- Normal CNAME publishing is subdomain-oriented; explicit root-domain publishing is listed on Convert.
- Official sources conflict on template count, published-page limits, visitor definitions, and simultaneous collaboration wording.
- Proprietary page export stays inside Instapage and omits important configuration when re-uploaded.
Landingi
Best for: Agencies and campaign teams that need many active pages, reusable operations, analytics, and plan-gated optimization features.
Landingi combines a conventional visual editor, forms, publishing, basic analytics, and higher-tier testing, subaccounts, and governance. Its production meter spans pages, visits, domains, users, and credits.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Landingi hosting, custom subdomains with SSL, WordPress, reverse proxy, and PHP wrapper publishing are documented. Root-domain workflows and every publishing method remain subscription-dependent. Sources: [landingi-publishing] |
| Templates, editor, and design control | Source-reviewed, not reproduced: The manual drag-and-drop editor documents 400+ templates plus blank starts, page and widget controls, desktop and mobile adjustment, undo or redo, history, and custom code paths. Sources: [landingi-editor] |
| Forms and lead delivery | Source-reviewed, not reproduced: Native fields, notifications, autoresponders, UTMs, stored leads, export, and CRM, email, payment, and webhook-style integration paths are documented. Delivery latency and duplicate behavior were not tested. Sources: [landingi-integrations] |
| Analytics, testing, and integration boundaries | Source-reviewed, not reproduced: Build includes basic analytics. Optimize adds EventTracker and server-side A/B testing. EventTracker documents click, scroll, form, lightbox, payment, UTM, and GA4 paths; configured results were not reproduced. Sources: [landingi-eventtracker], [landingi-pricing] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Metadata, custom meta tags, social fields, image alt text, headings, image optimization, and noindex are documented. Direct robots.txt control is unavailable; canonical and user-managed sitemap controls were not established. Sources: [landingi-seo] |
| Collaboration and governance | Source-reviewed, not reproduced: Current plans list 5, 10, or unlimited users; Scale adds subaccounts, agency controls, and audit logs. Official teamwork guidance says only one person and browser tab should edit a project at once. Sources: [landingi-team], [landingi-pricing] |
| Export and ownership | Source-reviewed, not reproduced: Pages transfer through proprietary landingpage files between active Landingi accounts. The PHP download references Landingi-hosted resources and is not a complete independent source export. Sources: [landingi-export] |
| Current pricing, traffic, and usage meters | Source-reviewed, not reproduced: Annual-effective Build is USD 24 for 10 active pages, 2,000 visits, one domain, five users, and 2,500 credits. Optimize is USD 119 for 100 pages, 30,000 visits, three domains, 10 users, and 10,000 credits. Monthly cash prices were not reliably exposed. Sources: [landingi-pricing] |
Tradeoffs
- Pages remain live only while the subscription is active, including wrapper-based publishing paths.
- Concurrent editing is explicitly unsafe; the documented workflow uses one active editor and page history.
- Project transfer is proprietary, and the PHP wrapper is not a standalone HTML, CSS, and JavaScript export.
Leadpages
Best for: Small performance-marketing teams that want hosted pages, forms, analytics, and built-in experimentation without a traffic cap.
Leadpages now combines AI-assisted or manual creation with forms, analytics, experiments, and standalone HTML export. Its 2026 live pricing table conflicts with recent help documentation on several quotas.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Leadpages URLs, custom domains, DNS setup, managed SSL, and paid hosted publishing are documented. Domain count depends on the current plan. Sources: [leadpages-getting-started], [leadpages-pricing] |
| Templates, editor, and design control | Source-reviewed, not reproduced: AI generation, a manual drag-and-drop visual editor, template starts, responsive previews, undo or redo, and HTML upload are documented as separate creation paths. Sources: [leadpages-getting-started] |
| Forms and lead delivery | Source-reviewed, not reproduced: Stored submissions, email notifications, honeypot filtering, CRM or email routing, webhooks, and CSV export are documented. Delivery, consent, retention after cancellation, and retry behavior were not reproduced. Sources: [leadpages-forms], [leadpages-pricing] |
| Analytics, testing, and integration boundaries | Source-reviewed, not reproduced: Pageviews, unique visitors, conversions, bounce rate, source, device, and UTM data are documented. Grow adds manual A/B testing; Optimize adds heatmaps and Smart Traffic; Scale adds continuous optimization. Sources: [leadpages-ab], [leadpages-pricing] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Managed CDN and SSL plus slugs, title, description, keywords, canonical, index or noindex, social fields, and favicon are documented. Uptime and page-speed claims are vendor statements, not test results. Sources: [leadpages-seo] |
| Collaboration and governance | Partially source-reviewed, not reproduced: Owner, Admin, and Member organizations plus version history and restoration are documented. Current pricing reserves workspaces and audit logs for Scale; formal approval and simultaneous co-editing were not established. Sources: [leadpages-organizations], [leadpages-pricing] |
| Export and ownership | Source-reviewed, not reproduced: Terms retain customer ownership of user content and data. The new builder supports standalone HTML export, including experiment variants, but not hosted analytics, integrations, optimization state, or full account configuration. Sources: [leadpages-terms], [leadpages-ab] |
| Current pricing, traffic, and usage meters | Source conflict, not reproduced: Regular monthly Grow, Optimize, and Scale are USD 99, USD 199, and USD 399; the live page shows USD 49 and USD 99 first-month promotions. Traffic and pages are listed unlimited, while domains, AI credits, integrations, seats, storage, and retention scale by plan. Recent help quotas conflict. Sources: [leadpages-pricing] |
Tradeoffs
- Regular monthly prices are materially higher than the temporary first-month promotion shown on the live page.
- Official pages disagree on page, domain, seat, integration, and experiment-variant quotas.
- HTML export does not carry hosted analytics, integrations, Smart Traffic, or the complete organization configuration.
Playcode custom page-to-app path
Best for: A custom landing experience that may need to grow into a form workflow, portal, dashboard, database-backed tool, or full-stack app.
Playcode is an AI app builder with a first-party runtime, not a dedicated campaign-optimization suite. It fits when the landing experience is only the first surface of custom software.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Playcode documents publishing, previews, HTTPS, custom domains, and full-stack Cloud apps under current plan limits and DNS setup. The configured campaign was not published for this comparison. Sources: [playcode-pricing], [playcode-cloud] |
| Templates, editor, and design control | Source-reviewed, not reproduced: Plain-language and visual iteration plus editable project code support custom page and application design. Output depends on the brief and review; this is not a fixed campaign-template inventory. Sources: [playcode-ai] |
| Forms and lead delivery | Partially source-reviewed, not reproduced: Custom forms, backend logic, database records, APIs, webhooks, or email paths can be built when the external path and credentials exist. No universal native lead-delivery connector or tested campaign flow is claimed. Sources: [playcode-cloud], [playcode-ai] |
| Analytics, testing, and integration boundaries | Unknown - not documented, not reproduced: The reviewed product pages do not establish a dedicated native campaign analytics dashboard, randomized landing-page A/B testing engine, traffic allocator, or statistical winner workflow. Custom integrations remain build work. Not tested. Sources: [playcode-ai], [playcode-cloud] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: Built-in keyword, backlink, SERP, and PageSpeed research plus custom code can support SEO and performance work. A tool result does not prove the generated page is fast, accessible, indexed, or ranking. Sources: [playcode-ai-seo] |
| Collaboration and governance | Partially source-reviewed, not reproduced: Current plans document collaboration boundaries, project history, previews, internal git, snapshots, and rollback. The reviewed pages do not establish a campaign-specific comment, approval, or experimentation-governance suite. Sources: [playcode-pricing], [playcode-cloud] |
| Export and ownership | Partially source-reviewed, not reproduced: Projects are real code and can be exported; Cloud adds git history, snapshots, and rollback on the supported path. External services, credentials, domains, analytics, and managed runtime state require a separate exit plan. Sources: [playcode-pricing], [playcode-cloud] |
| Current pricing, traffic, and usage meters | Source-reviewed, not reproduced: Pro is USD 25 monthly or USD 250 yearly with 100 AI credits per month. Current publishing, collaboration, bandwidth, and Cloud-app limits are separate production meters; external providers can add their own costs. Sources: [playcode-pricing] |
Tradeoffs
- Publisher relationship: Playcode publishes this guide and sells this product.
- Built-in campaign analytics, randomized A/B testing, CRM delivery, and formal approval workflows are not established as a dedicated native suite.
- A complete project export does not automatically reproduce managed runtime state, domains, external providers, analytics, or operational history.
Unbounce
Best for: Marketer-led paid campaigns that need a dedicated landing-page editor, traffic allocation, and plan-gated experimentation.
Unbounce is a hosted campaign platform with templates, forms, integrations, analytics, and higher-tier A/B testing or traffic optimization. Its production plan is metered by traffic, users, and root domains.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Managed hosting, custom-domain publishing, WordPress publishing, and SSL are documented. Root-domain count depends on plan, and trial publishing has separate restrictions. Sources: [unbounce-publishing], [unbounce-pricing] |
| Templates, editor, and design control | Source-reviewed, not reproduced: The current product documents 100+ templates, manual drag-and-drop editing, mobile layouts, reusable campaign elements, and custom HTML, CSS, or JavaScript on Build and higher. Sources: [unbounce-features], [unbounce-pricing] |
| Forms and lead delivery | Source-reviewed, not reproduced: Native and multi-step forms, lead storage, CSV export, notifications, webhooks, POST delivery, and CRM integrations are documented. A configured end-to-end delivery and retry path was not reproduced. Sources: [unbounce-leads], [unbounce-integrations] |
| Analytics, testing, and integration boundaries | Source-reviewed, not reproduced: Visitors, views, conversions, and conversion rate are built in. Experiment adds unlimited server-side A/B tests, variants, traffic allocation, and reporting; Optimize adds Smart Traffic and audience insights. Sources: [unbounce-pricing], [unbounce-features] |
| Performance and SEO controls | Partially source-reviewed, not reproduced: CDN delivery, SSL, image optimization, title and meta data, social image, alt text, and index or noindex are documented. Canonical UI, schema, sitemap controls, and measured page performance were not established. Sources: [unbounce-seo], [unbounce-features] |
| Collaboration and governance | Source conflict, not reproduced: Owner, Admin, Author, and Viewer roles plus client folders are documented. Live pricing caps users by plan, while a broad features page uses conflicting unlimited-user language. Audit logs are higher-tier. Sources: [unbounce-roles], [unbounce-pricing], [unbounce-features] |
| Export and ownership | Source-reviewed, not reproduced: Classic pages export only as proprietary Unbounce files for reuse inside Unbounce. Smart Builder pages cannot be downloaded, and no deployable HTML or complete account export is documented. Sources: [unbounce-export] |
| Current pricing, traffic, and usage meters | Source-reviewed, not reproduced: Monthly Starter, Build, Experiment, and Optimize are USD 29, USD 99, USD 149, and USD 249. Build includes unlimited pages, 20,000 monthly visitors, one user, and one root domain; Experiment raises traffic to 30,000, users to three, and domains to two. Overage is separate. Sources: [unbounce-pricing], [unbounce-overage] |
Tradeoffs
- A/B testing starts on Experiment rather than the lower Starter or Build plans.
- Traffic overages are billed account-wide even though pages remain live.
- Page transfer is proprietary, and Smart Builder does not provide a deployable source export.
Webflow
Best for: Design-heavy responsive campaign pages that belong inside a broader visual design system or marketing site.
Webflow provides detailed visual control, forms, SEO fields, domains, collaboration, and separate analytics or optimization products. Site plans, Workspaces, seats, Optimize, Analyze, and code export are separate boundaries.
| Criterion | Finding |
|---|---|
| Page publishing and domain | Source-reviewed, not reproduced: Starter publishes to a Webflow subdomain; each custom-domain production site needs a paid Site plan. Current plans document managed HTTPS, staging, and per-site publishing boundaries. Sources: [webflow-pricing] |
| Templates, editor, and design control | Source-reviewed, not reproduced: The visual Designer documents CSS-style classes, responsive breakpoints, reusable components, variants, interactions, and a landing-page template marketplace. Template quantity does not establish design fit. Sources: [webflow-design], [webflow-pricing] |
| Forms and lead delivery | Source-reviewed, not reproduced: Forms can use Webflow storage, email notifications, CSV export, webhooks, connected apps, or a custom action. Paid Site plans currently list unlimited submissions; the exported site needs an external form provider. Sources: [webflow-forms], [webflow-export], [webflow-pricing] |
| Analytics, testing, and integration boundaries | Partially source-reviewed, not reproduced: GA4, Tag Manager, and external measurement paths are documented. Webflow Analyze is an add-on, while current Optimize documentation gates native A/B/n and AI allocation to Enterprise. Basic does not include native testing. Sources: [webflow-optimize], [webflow-pricing] |
| Performance and SEO controls | Source-reviewed, not reproduced: CDN, SSL, image conversion, metadata, canonicals, sitemap, crawler controls, robots, redirects, schema through custom code, responsive breakpoints, and speed guidance are documented. The published fixture was not benchmarked. Sources: [webflow-seo], [webflow-pricing] |
| Collaboration and governance | Partially source-reviewed, not reproduced: Real-time collaboration, comments, site roles, publishing permissions, Reviewer seats, and site-specific access are documented. Advanced approvals, activity logs, and granular governance are plan-gated. Sources: [webflow-collaboration], [webflow-roles], [webflow-pricing] |
| Export and ownership | Source-reviewed, not reproduced: Paid Workspace plans can export HTML, CSS, JavaScript, and assets. CMS data, Ecommerce, User Accounts, localization, search, password protection, code components, and native form processing do not export. Sources: [webflow-export] |
| Current pricing, traffic, and usage meters | Source-reviewed, not reproduced: Basic is USD 15 monthly billed yearly or USD 25 month-to-month with one custom-domain site, 300 static pages, 10 GB bandwidth, and unlimited forms. Premium is USD 25 yearly or USD 39 monthly; Workspace, seats, CMS, Analyze, Optimize, and overages are separate. Sources: [webflow-pricing] |
Tradeoffs
- The entry Basic Site plan does not include CMS or the Enterprise-gated native Optimize product.
- A paid Site plan and paid Workspace solve different jobs and can create separate bills.
- Static source export excludes CMS data, Ecommerce, localization, search, password protection, code components, and native form processing.
Choose the shortest eligible shortlist
A provider enters the shortlist only when it clears every required documented boundary or has an owned pilot for the unknown. Compare remaining options by operating responsibility, unresolved risk, and complete production meter.
The campaign requires native randomized tests and traffic allocation.
Choose: Start with the exact Unbounce Experiment, Instapage Optimize, Leadpages Grow or higher, or Landingi Optimize plan that documents the needed testing path.
Tradeoff: Plan access is not proof of clean assignment, event integrity, statistical interpretation, or conversion lift. Reproduce one controlled experiment.
The campaign must live inside a CRM, contact, and automation system.
Choose: Shortlist HubSpot when the contact record and governed campaign workflow matter more than a standalone page subscription.
Tradeoff: Seats, contacts, Hub tier, credits, automation, and page scale can make the full meter larger than the landing-page headline price.
The page is intentionally simple and annual cost is the primary constraint.
Choose: Shortlist Carrd Pro Standard, then move to Pro Plus only if advanced delivery, canonical or redirect control, or source download is required.
Tradeoff: You may need external analytics, experimentation, automation, and form operations, and the export does not preserve Carrd-dependent services.
The campaign belongs inside a larger high-control marketing site.
Choose: Shortlist Webflow when responsive design systems, broader page architecture, and detailed SEO controls matter more than bundled self-serve experimentation.
Tradeoff: Price the Site plan, Workspace, seats, CMS, Analyze, Optimize, and export boundary separately.
The landing experience must become custom workflow software.
Choose: Shortlist Playcode only when custom forms, records, roles, portals, dashboards, or backend behavior are the actual next rung.
Tradeoff: Plan and build the campaign analytics, experimentation, delivery, and governance path explicitly; Playcode is not a dedicated CRO suite.
Traffic is uncertain or can spike.
Choose: Model the same high month against visitor caps and overages for Unbounce, Instapage, and Landingi, then compare Leadpages, Carrd, HubSpot, Webflow, and Playcode on their actual non-traffic meters.
Tradeoff: Providers define visits, visitors, sessions, bandwidth, contacts, and traffic differently. Do not compare unlike units as though they were one number.
Portability is a required gate.
Choose: Export the page, assets, form data, redirects, tracking configuration, experiment state, and one runnable copy before selecting the provider.
Tradeoff: Carrd, Leadpages, HubSpot, Webflow, and Playcode document different export paths; none makes every hosted behavior portable automatically.
NEED A CUSTOM NEXT RUNG?
Prototype the campaign workflow before choosing the platform
Describe the page, form, record, delivery path, analytics events, user roles, export requirement, and one failure case. Review the working slice before committing to a platform.
Start BuildingThis ordinary blog page is AI-credit-ineligible. Eligible new users receive AI credits when they start building; production limits and external-provider responsibilities still apply.
Check current Playcode plan limitsPlaycode is the disclosed publisher option; verify the live plan before purchase.
Evidence, testing, and disclosure limits
This page records dated documentation and a reproducible selection method. It does not convert vendor documentation into an observed product result.
- We did not purchase every plan, publish the same page in every provider, deliver leads to a controlled CRM, run randomized tests, contact support, or reproduce export, migration, restore, cancellation, or overage behavior.
- Playcode publishes this guide and appears as the disclosed custom page-to-app path. Outbound provider links contain no affiliate parameters, Playcode receives no referral compensation, and alphabetical order is not a rank.
- Prices, promotions, plan names, traffic definitions, pages, domains, seats, contacts, storage, credits, integrations, add-ons, overages, taxes, and regional availability can change before the August 31 review date.
- Vendor claims about speed, uptime, optimization, templates, conversion readiness, security, accessibility, or SEO are not independent test results.
- Unknown means the reviewed official pages did not establish the behavior. It does not prove the provider lacks it. Every unknown remains not tested.
- Source conflict means current first-party pages disagree. We preserve the conflict and direct the buyer to the live checkout or account screen instead of selecting a convenient value.
- A code or HTML export does not automatically preserve forms, contacts, CMS data, analytics, experiments, redirects, domains, connected providers, permissions, or a complete runnable service.
- There is no universal winner. Fit changes with the campaign contract, required gates, team, traffic, suppliers, current quote, reproduced pilot, and acceptable exit.
First-party sources checked August 1, 2026
Every material finding maps to an official provider page. Access dates record our review, not an invented publication date for undated documentation.
[carrd-plans] Carrd:Carrd Pro plans
Checked August 1, 2026. Supports: Current tiers, annual prices, site counts, and plan-gated features.
[carrd-domain] Carrd:Using a custom domain
Checked August 1, 2026. Supports: Custom root or subdomain publishing, DNS, and SSL boundary.
[carrd-building] Carrd:Carrd building overview
Checked August 1, 2026. Supports: Templates, blank canvas, responsive editor, sections, and preview workflow.
[carrd-forms] Carrd:Carrd form configuration
Checked August 1, 2026. Supports: Contact-form fields, email recipients, and standard form boundary.
[carrd-analytics] Carrd:Carrd site analytics
Checked August 1, 2026. Supports: External analytics integrations and the absence of a documented native test result.
[carrd-seo] Carrd:Carrd site files and SEO controls
Checked August 1, 2026. Supports: Automatic sitemap plus plan-related SEO control boundary.
[carrd-sharing] Carrd:Sharing access to a Carrd site
Checked August 1, 2026. Supports: Admin, Editor, and Template access roles.
[carrd-export] Carrd:Downloading a Carrd site
Checked August 1, 2026. Supports: Static source export, unsupported hosted features, and no re-import boundary.
[hubspot-content-pricing] HubSpot:HubSpot Content Hub pricing
Checked August 1, 2026. Supports: Current plan, seat, page, credit, promotional, and standard pricing boundaries.
[hubspot-pages] HubSpot Knowledge Base:Create and customize HubSpot pages
Checked August 1, 2026. Supports: Page limits, templates, editor, custom domains, page settings, and SEO controls.
[hubspot-domain] HubSpot Knowledge Base:Connect a domain to HubSpot
Checked August 1, 2026. Supports: DNS, domain connection, permissions, and publishing prerequisites.
[hubspot-landing-pages] HubSpot:HubSpot landing pages
Checked August 1, 2026. Supports: Forms, meetings, CRM contacts, page building, and reporting workflow.
[hubspot-ab] HubSpot Knowledge Base:Run an A/B test on a page
Checked August 1, 2026. Supports: Subscription gate, variants, traffic split, performance review, and winner workflow.
[hubspot-analytics] HubSpot Knowledge Base:Analyze page performance
Checked August 1, 2026. Supports: Page-performance reporting boundary.
[hubspot-permissions] HubSpot Knowledge Base:HubSpot user permissions guide
Checked August 1, 2026. Supports: View, edit, publish, domain, private-content, and user-management permissions.
[hubspot-export] HubSpot Knowledge Base:Export web content and data
Checked August 1, 2026. Supports: HTML page, post, template, and content-data export boundary.
[instapage-plans] Instapage:Instapage plans
Checked August 1, 2026. Supports: Current prices, visitors, pages, domains, members, editor, test, and enterprise gates.
[instapage-publishing] Instapage Help Center:Instapage publishing options
Checked August 1, 2026. Supports: Custom domain, WordPress, Drupal, and test-domain publishing paths.
[instapage-leads] Instapage Help Center:Instapage lead management
Checked August 1, 2026. Supports: Lead storage, notification, recipient, and export behavior.
[instapage-analytics] Instapage Help Center:Instapage analytics overview
Checked August 1, 2026. Supports: Visits, conversions, bounce rate, and conversion-rate reporting.
[instapage-integrations] Instapage:Instapage integrations catalog
Checked August 1, 2026. Supports: Native, Zapier, and external-app integration categories.
[instapage-seo] Instapage Help Center:Instapage Search and Social settings
Checked August 1, 2026. Supports: Metadata, canonical, indexation, social, schema, and robots boundary.
[instapage-team] Instapage Help Center:Manage Instapage team members
Checked August 1, 2026. Supports: Role and single-active-editor collaboration boundary.
[instapage-export] Instapage Help Center:Download and upload Instapage pages
Checked August 1, 2026. Supports: Proprietary transfer format, missing settings, and no HTML export.
[instapage-usage] Instapage Help Center:Instapage usage limits
Checked August 1, 2026. Supports: Traffic counter, warning, lock, and plan-limit boundary.
[landingi-pricing] Landingi:Landingi pricing
Checked August 1, 2026. Supports: Prices, active pages, visits, domains, users, credits, analytics, tests, and governance.
[landingi-publishing] Landingi Help Center:Landingi publishing options
Checked August 1, 2026. Supports: Hosted, domain, WordPress, proxy, wrapper, SSL, and subscription boundaries.
[landingi-editor] Landingi Help Center:Landingi editor overview
Checked August 1, 2026. Supports: Templates, widgets, page controls, mobile editing, preview, and history.
[landingi-integrations] Landingi Help Center:Landingi integrations overview
Checked August 1, 2026. Supports: Form delivery to email, CRM, payment, automation, and other providers.
[landingi-eventtracker] Landingi Help Center:Landingi EventTracker
Checked August 1, 2026. Supports: Page events, filters, UTM, variants, and GA4 delivery boundary.
[landingi-seo] Landingi Help Center:Landingi SEO settings
Checked August 1, 2026. Supports: Metadata, custom tags, social fields, images, headings, and indexing controls.
[landingi-team] Landingi Help Center:Landingi teamwork guidance
Checked August 1, 2026. Supports: Single-editor constraint, save conflict, and page-history recovery boundary.
[landingi-export] Landingi Help Center:Landingi page export and import
Checked August 1, 2026. Supports: Proprietary project transfer and hosted dependency boundary.
[leadpages-pricing] Leadpages:Leadpages pricing
Checked August 1, 2026. Supports: Regular and promotional prices, traffic, pages, domains, credits, integrations, seats, and retention.
[leadpages-getting-started] Leadpages Support:Leadpages first-page workflow
Checked August 1, 2026. Supports: AI, visual editor, HTML, publishing, and page-creation paths.
[leadpages-forms] Leadpages Support:Leadpages forms
Checked August 1, 2026. Supports: Stored leads, notifications, spam protection, and integration delivery.
[leadpages-ab] Leadpages Support:Leadpages A/B testing
Checked August 1, 2026. Supports: Variants, goals, traffic allocation, results, optimization, and HTML export.
[leadpages-seo] Leadpages Support:Leadpages page settings
Checked August 1, 2026. Supports: Slug, metadata, canonical, indexation, social, favicon, and protection controls.
[leadpages-organizations] Leadpages Support:Leadpages organizations and teams
Checked August 1, 2026. Supports: Owner, Admin, Member, organization, page ownership, and analytics access boundaries.
[leadpages-terms] Leadpages:Leadpages terms
Checked August 1, 2026. Supports: Customer user-content and customer-data ownership boundary.
[playcode-pricing] Playcode:Playcode pricing
Checked August 1, 2026. Supports: Current AI credits, publishing, collaboration, code export, bandwidth, and Cloud-app limits.
[playcode-cloud] Playcode:Playcode Cloud
Checked August 1, 2026. Supports: Runtime, database, files, HTTPS, domains, history, snapshots, rollback, and export boundary.
[playcode-ai-seo] Playcode:Playcode AI SEO
Checked August 1, 2026. Supports: Keyword, backlink, SERP, PageSpeed, and on-page improvement workflow.
[playcode-ai] Playcode:Playcode AI builder
Checked August 1, 2026. Supports: Plain-language build, visual iteration, editable project, and custom software boundary.
[unbounce-pricing] Unbounce:Unbounce pricing
Checked August 1, 2026. Supports: Current price, pages, traffic, users, domains, forms, tests, and optimization plan gates.
[unbounce-publishing] Unbounce Documentation:Publishing an Unbounce page
Checked August 1, 2026. Supports: Hosted, custom-domain, WordPress, test, and subscription publishing paths.
[unbounce-features] Unbounce:Unbounce product features
Checked August 1, 2026. Supports: Templates, editor, forms, analytics, testing, integrations, CDN, and broad feature claims.
[unbounce-leads] Unbounce Documentation:Getting Unbounce leads
Checked August 1, 2026. Supports: Lead table, notifications, and CSV export.
[unbounce-integrations] Unbounce Documentation:Unbounce integrations
Checked August 1, 2026. Supports: Webhook, POST, CRM, marketing automation, and third-party delivery paths.
[unbounce-seo] Unbounce Documentation:Unbounce SEO guidance
Checked August 1, 2026. Supports: Metadata, images, indexation, and documented SEO-control boundary.
[unbounce-roles] Unbounce Documentation:Unbounce user role permissions
Checked August 1, 2026. Supports: Owner, Admin, Author, and Viewer permission boundaries.
[unbounce-export] Unbounce Documentation:Download or upload an Unbounce page
Checked August 1, 2026. Supports: Classic proprietary transfer, Smart Builder limitation, and no HTML export.
[unbounce-overage] Unbounce Documentation:Unbounce traffic overages
Checked August 1, 2026. Supports: Traffic pooling, notification, page-live, and overage-charge behavior.
[webflow-pricing] Webflow:Webflow pricing
Checked August 1, 2026. Supports: Current Site and platform prices, pages, bandwidth, forms, SEO, roles, Analyze, Optimize, and Cloud meters.
[webflow-design] Webflow Help Center:Webflow components overview
Checked August 1, 2026. Supports: Reusable components, variants, visual design systems, and page construction boundary.
[webflow-forms] Webflow Help Center:Webflow form submissions
Checked August 1, 2026. Supports: Stored submissions, notifications, CSV export, and custom-action behavior.
[webflow-optimize] Webflow Help Center:Introduction to Webflow Optimize
Checked August 1, 2026. Supports: A/B/n, AI allocation, analytics, and Enterprise add-on boundary.
[webflow-seo] Webflow Help Center:Webflow site-speed and SEO controls
Checked August 1, 2026. Supports: Hosting, image, asset, script, font, and performance-control guidance.
[webflow-collaboration] Webflow Help Center:Webflow real-time collaboration
Checked August 1, 2026. Supports: Concurrent editing, presence, page coordination, and collaboration behavior.
[webflow-roles] Webflow Help Center:Webflow site roles and permissions
Checked August 1, 2026. Supports: Site roles, publishing permissions, access, and plan boundaries.
[webflow-export] Webflow Help Center:Export Webflow site code
Checked August 1, 2026. Supports: Static source export, Workspace requirement, and excluded hosted functionality.
Landing page builder FAQ
What is the best landing page builder in 2026?
There is no universal winner. Choose by required job: Carrd for a simple low-cost page, HubSpot for a CRM-connected campaign, Instapage or Unbounce for paid acquisition, Landingi for campaign operations, Leadpages for built-in CRO without traffic caps, Webflow for design systems, or Playcode for a custom page-to-app path.
Did Playcode test all eight landing page builders?
No. We reviewed first-party documentation and current pricing on August 1, 2026. We did not purchase every plan or reproduce one controlled campaign across all eight providers. Every finding is marked not reproduced, and the evidence pack supplies the fixture and pilot protocol needed to run that work.
Which landing page builders include A/B testing?
Current official sources document A/B testing on Unbounce Experiment, Instapage Optimize, Leadpages Grow and higher, and Landingi Optimize and higher. HubSpot documents page A/B tests on Content Hub Professional or Enterprise. Webflow Optimize is an Enterprise add-on. Carrd and Playcode did not establish a dedicated native test engine in the reviewed pages.
Which landing page builder has no traffic cap?
Leadpages currently lists unlimited traffic and pages, while Carrd does not publish a native traffic meter for its simple sites. Unbounce, Instapage, and Landingi publish traffic or visit allowances. HubSpot, Webflow, and Playcode use different meters such as pages, contacts, bandwidth, seats, credits, apps, or runtime limits. Compare definitions before comparing numbers.
Can I export a landing page and host it elsewhere?
It depends on the product and plan. Carrd Pro Plus, the new Leadpages builder, paid Webflow Workspaces, HubSpot exports, and Playcode document source or HTML paths with different exclusions. Instapage, Landingi, and Unbounce use proprietary transfer formats. Even static source rarely preserves hosted forms, analytics, experiments, CMS data, permissions, or integrations.
Is a landing page builder the same as a website builder?
No. A landing-page platform usually centers one campaign action, lead delivery, attribution, and testing. A website builder emphasizes broader navigation, content, design systems, CMS, commerce, or business operations. Webflow, HubSpot, and Playcode cross the boundary in different ways; the correct category depends on the whole job.
Can a landing page builder guarantee more conversions?
No. A builder can provide editing, publishing, forms, analytics, and experiments, but results also depend on the audience, offer, proof, traffic quality, consent, delivery, measurement, sample size, and operating decisions. Vendor conversion claims and templates are not a guarantee for your campaign.
How should I compare landing page builder pricing?
Price the lowest plan that satisfies the frozen campaign. Count regular and promotional price, billing term, traffic, pages, domains, seats, contacts, storage, credits, integrations, analytics retention, testing, add-ons, overages, implementation, and operator time. Recheck the live checkout because every price and meter in this guide is volatile.
BUILD THE PILOT
Test the page-to-app path with your real campaign contract
Describe the page, fields, consent, delivery path, analytics events, roles, domain, export need, and one failure case. Playcode can build the smallest custom slice for review.
Start with PlaycodePlaycode is the publisher and custom page-to-app option, not an independent evaluator, traffic platform, CRM, or automatic conversion optimizer.