WordPress.com

Proprietary hosted service owned and operated by Automattic; runs a modified version of the WordPress software but is not affiliated with the WordPress Foundation or the WordPress.org open-source project.

Launched November 21, 2005, by Automattic founder Matt Mullenweg, as a hosted version of the WordPress software he co-created in 2003.

Fully managed, hosted WordPress product; scope of this listing is the hosted .com product, distinct from self-hosted WordPress.org (listed separately in this dataset).

The underlying WordPress core software is GPL open source, but WordPress.com as a hosted service is a proprietary, closed commercial platform with Automattic-controlled infrastructure, plan gating, and Terms of Service. You cannot self-host or fork "WordPress.com" itself.

The service/business itself is not licensed to the public the way the underlying software is; standard commercial Terms of Service apply to the hosted product.

Best fit narrows compared to WordPress.org: it trades some flexibility (managed environment, plan-gated plugins/themes, no root server access) for zero-maintenance hosting.

Free plan exists indefinitely with no expiration, hosted on a wordpress.com subdomain.

Unlimited pages/posts/users/visitors on Free, but the domain and branding restrictions are the practical dealbreakers for a business site.

Functionally trial-like since you can upgrade, use paid features, and get a full refund within the window if unsatisfied.

Personal plan: $4/mo billed annually ($48/yr) is the cheapest tier that includes a free custom domain; $9/mo if billed monthly. The Free plan cannot use a custom domain at all.

Premium plan at $8/mo billed annually ($96/yr) is WordPress.com's positioned mid-tier for creators/monetizing sites (payment buttons, VideoPress, advanced analytics); Business at $25/mo annually is the step-up for full plugin/theme freedom and priority support.

Commerce plan: $45/mo billed annually ($540/yr), $70/mo if billed monthly. This is the dedicated WooCommerce-integrated store tier with 0% WordPress.com transaction fees; basic payment buttons exist on lower tiers but full store functionality requires Commerce.

The Free plan both shows platform ads to visitors and forces a wordpress.com subdomain; both go away starting at Personal.

Unlike many hosts that lure with a low intro rate then increase renewal price, WordPress.com's published monthly-equivalent price for a given billing term (monthly/annual/2-year/3-year) is the standard ongoing rate at that term, not a limited-time discount. Prices can still change over time platform-wide, and the domain's first year is discounted, but there is no bait-and-switch renewal jump built into the plan pricing itself.

14-day refund window for annual and multi-year plan purchases/renewals; 7 days for monthly plans. Domain registrations have a separate, shorter 96-hour (4-day) refund window, and a 100-year plan carries a 120-day window.

Total cost of ownership is far more predictable than self-hosted WordPress.org because hosting/security/updates are bundled into the plan price rather than sourced separately.

Same Gutenberg block editor and full Site Editor (theme.json-powered global styles, template editing) as WordPress.org, run in Automattic's managed environment.

Blocks can be reordered via drag-and-drop; media can be drag-and-dropped into the uploader, identical to core WordPress block editor behavior.

Click-to-edit text directly within blocks in the WYSIWYG block editor.

In-editor undo/redo plus full post/page revision history; Business/Commerce plans add real-time full-site backup restore points on top of content revisions.

Native autosave of drafts in the block editor, same behavior as WordPress.org.

Official WordPress/Jetpack mobile apps (iOS/Android) support full post/page editing, block editing, and media upload for WordPress.com sites.

Same underlying risk as WordPress.org: switching themes can break custom layouts and block placements. WordPress.com's curated/vetted theme catalog and Global Styles reduce breakage risk somewhat versus arbitrary third-party WordPress.org themes, but it is not guaranteed content-preserving.

Editorial judgment: publishing via the block editor is approachable and hosting/maintenance is fully handled by Automattic (easier than WordPress.org), but the block editor and Site Editor still have more depth than a pure drag-and-drop builder like Wix or Squarespace, and plan-gating adds a layer of "which tier unlocks this" decision-making for new users.

WordPress.com's theme showcase does not publish an exact total count (marketing copy says "thousands of free and premium themes"); it draws from the same WordPress.org free theme directory (8,353 themes per that listing) plus WordPress.com-exclusive premium and partner themes layered on top, so no single official number exists.

Native Font Library for uploading custom font files on block themes, available on all paid plans as part of the Global Styles unlock (Free plan has limited styling options).

Site Editor includes a desktop/tablet/mobile viewport preview toggle and block-level responsive settings on block themes; full arbitrary breakpoint CSS control requires Custom CSS (Personal+) or Business-plan custom code, so out-of-the-box control sits between fully automatic and fully open.

As of the April 2026 plan overhaul, Custom CSS and Global Styles are included on every paid plan starting at Personal ($4/mo annual); not available on the Free plan.

Arbitrary custom JavaScript/code injection is a Business-plan-and-up capability (via SFTP/SSH, WP-CLI, Git/GitHub Deployments, or code-block plugins that themselves require Personal+ for plugin access); not available on Free, and only plugin-mediated (not raw file/theme code) on Personal/Premium.

No native visual animation/interaction builder in the Site Editor; achieved via plugins (available Personal+) or custom CSS/JS (Business+), same gap as WordPress.org core.

theme.json-powered Global Styles panel (colors, typography, spacing) on block themes, included on all paid plans since the April 2026 change; not on Free.

Editorial judgment: with plugins/custom CSS now open from Personal up and full custom code/SFTP on Business, WordPress.com narrows the flexibility gap with WordPress.org considerably versus its older, more locked-down plan structure. It still falls short of "unconstrained" because core files stay Automattic-managed (no root server access even on Business), some plugins/services are disallowed for platform stability/security reasons, and the Free tier is template-bound. Landing on moderate rather than unconstrained to reflect that managed-platform ceiling.

Fully managed hosting is the core premise of WordPress.com across every plan, including Free.

WordPress.com sites run exclusively on Automattic's infrastructure; there is no option to self-host a "WordPress.com" site. Site owners wanting self-hosting must migrate content to separate WordPress.org software on their own host.

Automattic's global CDN and edge caching (via Jetpack's underlying infrastructure) are included automatically on every WordPress.com site at no extra charge.

Free SSL certificates are automatically provisioned and included for every WordPress.com site, custom domain or subdomain, on all plans including Free.

Automattic publishes a public status/incident history page (automatticstatus.com) for transparency, but this is historical reporting, not a contractual guarantee with penalties/credits like some managed hosts offer. Enterprise-tier WordPress VIP (a separate Automattic product) does publish a formal platform SLA, but that is out of scope for standard WordPress.com plans.

Video specifically is stored via VideoPress with its own separate allotment (250 GB on Business/Commerce) that doesn't count against the base storage figure.

No native one-click static-site export/generation feature for WordPress.com sites; the platform is architected as a managed dynamic CMS. Content can be exported as WXR/XML and migrated elsewhere, but that is a content migration path, not a static HTML export of the live site.

HTTP Archive CWV Technology Report tracks "WordPress.com" as its own distinct technology, separate from the general "WordPress" (self-hosted) entry. Latest available month (May 2026, CrUX data): 70.5% of 96,252 combined desktop+mobile origins passed all Core Web Vitals (desktop 65.9% of 34,391; mobile 73.0% of 61,861). Notably higher than self-hosted WordPress's 50.7% in this dataset, consistent with WordPress.com running on Automattic-optimized, uniformly-configured managed infrastructure rather than the highly variable hosting quality across the self-hosted ecosystem.

Automattic's Photon/Jetpack image CDN automatically serves resized, compressed, and modern-format (WebP) images site-wide on WordPress.com by default, unlike bare WordPress.org core which lacks this without a plugin.

Native lazy-loading for images, inherited from WordPress core (default since version 5.5) and reinforced by Jetpack's performance features.

Page/edge caching is handled automatically by Automattic's managed infrastructure; site owners do not get direct cache-control configuration (no server-level caching plugin/config access) the way a self-hosted WordPress.org site owner does, even on Business/Commerce with SFTP access, since core caching layers remain platform-managed.

Basic excerpt/description editing is available on all plans; the dedicated SEO Tools panel for full custom meta titles/descriptions with live previews and custom title-tag formatting requires Premium, Business, or Commerce (not Free or Personal).

Native permalink/slug editing for every post and page on all plans, including Free.

Once on a custom domain (Personal+), URL flexibility closely matches WordPress.org.

No native redirect manager; WordPress.com's own support documentation directs users to install a plugin (Redirection, or 301 Redirects) to manage 301s. Since plugin installation itself now requires Personal plan or higher, page-level redirects are effectively gated behind Personal+.

Self-referencing canonical tags are output automatically on all plans (inherited from WordPress core behavior); the SEO Tools panel (Premium+) adds the ability to add canonical URLs to archive pages specifically.

Native "discourage search engines from indexing this site" toggle in site visibility/privacy settings controls the robots meta output; this is a site-wide switch rather than direct raw robots.txt file editing, matching WordPress core's virtual-robots.txt behavior.

XML sitemap automatically generated and enabled by default at yoursite.com/sitemap.xml for every WordPress.com site (via built-in Jetpack functionality), including image/video sitemaps and a News sitemap; limited to 1,000 recently-updated posts per the support docs. No manual setup required on any plan.

No dedicated native schema.org/JSON-LD markup builder documented for WordPress.com beyond what Jetpack outputs for specific content types (e.g., Publicize-related markup); comprehensive custom structured data (Article, Product, FAQ, etc.) requires an SEO/schema plugin, available starting at the Personal plan once plugin access is unlocked.

No native hreflang generation; requires a multilingual plugin (WPML or Polylang), both of which generate hreflang tags automatically once installed. Plugin installation requires Personal plan or higher.

Jetpack's built-in Social/Publicize features generate Open Graph and Twitter Card meta tags automatically once a social connection module is active; the Premium+ SEO Tools panel adds further social preview controls.

The native "discourage search engines" control documented in WordPress.com's own privacy settings is a site-wide toggle, not a per-page/per-post noindex field; true per-page noindex requires an SEO plugin (available Personal+).

Native alt text field in the Media Library and block editor's image block on every plan, including Free.

Blogging (Posts) is native and central to WordPress.com, inherited from WordPress core, available on every plan including Free.

Unlike self-hosted WordPress.org (where register_post_type() is a core PHP API any developer can call), WordPress.com site owners without server/code access rely on plugins (e.g., Advanced Custom Fields, Pods) or Business-plan custom code to create true custom post types/collections; not a point-and-click native feature in the dashboard.

Categories and tags are native taxonomies on every plan, inherited from WordPress core.

Native "Publish" date/time scheduling for posts and pages on every plan, including Free.

Native post/page revision history and restore, same as WordPress core; Business/Commerce additionally layer on real-time full-site backups with one-click restore.

Native roles (Administrator, Editor, Author, Contributor, Subscriber, plus a WordPress.com-specific Viewer role for private sites) support multi-author workflows on every plan.

Native RSS feeds auto-generated for posts, categories, tags, and comments on every WordPress.com site, no setup required.

WordPress.com's public REST API (developer.wordpress.com) supports reading public content openly and writing content via OAuth2-authenticated requests; same read/write capability model as the WordPress.org REST API, hosted and managed by Automattic.

Commerce plan bundles fully managed WooCommerce (store setup, hosting, and store tools included without needing to separately install/host WooCommerce); lower plans support only simple payment buttons (PayPal/Stripe), not a full storefront.

Practical ceiling at very large catalog sizes is server/database performance, not a stated plan limit, matching WooCommerce's behavior on WordPress.org.

This tiered platform fee (separate from payment processing) is a meaningful cost difference from self-hosted WordPress.org + WooCommerce, which charges 0% platform fee at every tier.

Gateway breadth on Commerce approaches WordPress.org + WooCommerce; lower tiers are far more limited since they lack a real checkout/cart system.

Commerce plan explicitly supports digital downloads with instant delivery; Premium plan payment buttons can also sell simple digital/paid content via paid content gating.

Commerce plan lists subscription/recurring revenue models as a supported product type via the bundled WooCommerce Subscriptions-class functionality; Premium plan also supports simple recurring payment buttons for memberships/donations at a smaller scale.

Commerce plan explicitly advertises selling in 60+ countries and accepting 135+ currencies as a built-in capability, not requiring a separate paid extension the way base WooCommerce on WordPress.org typically does.

Commerce plan includes in-person payments/point-of-sale support for the US and Canada via the Woo mobile app and card-reader integration.

Commerce plan includes built-in abandoned cart recovery as part of its bundled email marketing automation, without needing a separate paid extension purchase (unlike bare WooCommerce on WordPress.org, which typically requires an add-on for this).

This bundling is a meaningful convenience/cost advantage over assembling the same stack manually on WordPress.org.

Native export tool produces a complete WXR (WordPress eXtended RSS/XML) file covering posts, pages, comments, categories, and tags, on any plan including Free; available at any time, no plan restriction found in official docs.

Design/theme and plugin configuration do not travel with a standard content export, only post/page/comment content.

Business/Commerce plans provide SFTP/SSH and phpMyAdmin database access, but core WordPress files remain Automattic-managed and are not downloadable via SFTP; a full like-for-like design/site copy to another host requires a migration plugin (e.g., All-in-One WP Migration) or manual theme rebuild, not a single clean export. Free through Premium have no file-level access at all.

Domains registered or connected through WordPress.com can be transferred out to another registrar at any time (after unlocking and obtaining an auth code), per official domain-transfer documentation. No lock-in on the domain itself.

This is the defining structural difference from WordPress.org: a WordPress.com site cannot be picked up and run on other infrastructure as-is. Content can be exported/migrated (see ownership.content_export), but the live site itself only runs on Automattic's managed platform.

The public WordPress.com REST API exposes full read access to public content and authenticated read/write access to private/owned content, matching the WordPress.org REST API's content model.

Editorial judgment: content (posts/pages/comments) exports cleanly via WXR on any plan, which caps the downside meaningfully below a true walled-garden builder like Wix or Squarespace. But hosting itself is not portable (site only runs on Automattic's infrastructure), design/theme migration is only partial even on Business/Commerce, and plugin/ecommerce configuration doesn't travel with a standard export. That combination lands WordPress.com in the middle: safer to leave than a proprietary hosted builder, but with real friction versus WordPress.org's "just move the files and database" portability.

Same underlying plugin directory as WordPress.org, so ecosystem size is effectively shared; the meaningful difference is plan-gating (not available on Free) rather than a smaller catalog.

Native, documented public REST API (developer.wordpress.com) available for every WordPress.com site, with OAuth2 authentication for write access.

Native to WooCommerce on the Commerce plan (order/product webhooks, same as WordPress.org's WooCommerce); general-purpose outbound webhooks outside ecommerce typically require a plugin, available Personal+.

Custom code blocks/header-footer injection require either a plugin (Personal+) or, for full theme-file-level custom code, SFTP/SSH/Git access on Business and Commerce. Not available on Free.

Developer tooling (WP-CLI, Git deploys) is a Business-plan-and-up feature, not available on lower tiers.

WP-CLI access is included on Business and Commerce plans via SSH; not available on Free, Personal, or Premium.

Via plugin (Zapier's official WordPress plugin, Make via REST API), same integration path as WordPress.org; requires Personal plan or higher for plugin installation, plus WooCommerce-specific Zapier support on Commerce.

First-party integration depth is notably deeper out-of-the-box than WordPress.org, where equivalent functionality (stats, CDN, image optimization) requires installing and configuring Jetpack or comparable plugins yourself.

The built-in AI Assistant can generate and modify full page layouts, colors, and fonts through the Appearance/Site Editor via natural-language prompts, going beyond copy drafting into structural site generation.

Native AI Assistant handles drafting, rewriting for tone/clarity, and title generation directly inside the block editor. Free plan gets 20 lifetime requests; unlimited(-ish) fair-use access is included on all paid plans (Personal and up).

Native AI image generation and editing within the block editor and Media Library (e.g., "generate an image of X"), included in the same AI Assistant feature as copy generation.

The Premium+ SEO Tools panel includes AI-powered metadata generation for titles/descriptions; separate from the general-purpose AI Assistant.

Architecturally opposite approach from WordPress.org: WordPress.com ships one integrated first-party assistant, WordPress.org ships a provider-agnostic framework for others to build on.

Six-role hierarchical system (Administrator, Editor, Author, Contributor, Subscriber, plus a WordPress.com-specific Viewer role for private sites) where each role inherits the capabilities of the one below it. This is simpler and less customizable than WordPress.org's granular, individually-assignable capability system (add_cap/remove_cap), per WordPress.com's own documentation contrasting the two.

Post-locking prevents two users from editing the same post simultaneously and shows a "someone else is editing" notice, inherited from WordPress core; not true simultaneous co-editing (like Google Docs).

Native "Pending Review" post status exists for Contributors, but structured multi-step editorial approval workflows require a plugin (e.g., PublishPress), available starting at the Personal plan.

True staging site environments (a full clone of the production site for testing changes, with two-way database/file sync back to production) are a native, one-click feature on Business and Commerce plans; production and staging share the plan's storage allocation 50/50. Lower plans get preview-only (draft preview before publishing), same as WordPress.org core.

The AI Assistant's collaborative block notes support @ai mentions for in-editor commentary/fact-checking on drafts, a WordPress.com-specific capability not present in bare WordPress.org core (which has no native in-editor commenting as of this dataset's WordPress.org entry).

No dedicated native admin-action audit/activity log surfaced in official plan-feature documentation; Business/Commerce activity/backup history logs changes for restore purposes but is not documented as a general-purpose security audit log the way a plugin like WP Activity Log provides on WordPress.org.

Support channel breadth scales directly with plan tier, unlike WordPress.org where support is entirely community-forum-based regardless of "plan" since there is no vendor plan.

24/7 priority support from Automattic's own support staff ("Happiness Engineers") is included on Business and Commerce plans; lower tiers get email/community support without a 24/7 guarantee.

Editorial judgment: wordpress.com/support provides extensive, actively maintained, plan-aware official documentation (per-plan feature pages, guided courses like the SEO course referenced above, developer docs at developer.wordpress.com), on par with WordPress.org's documentation depth and easier to navigate for non-technical users since it's written for a single managed product rather than a sprawling ecosystem.

Community size is shared with the broader WordPress ecosystem rather than being a WordPress.com-exclusive figure; treat the 43% stat as approximate and covering all WordPress deployments, not .com alone.

No SOC 2, ISO 27001, or similar third-party security certification found published specifically for the standard WordPress.com consumer/business product. Automattic's separate enterprise product, WordPress VIP, does hold SOC 2 Type I attestation and other enterprise certifications, but that is a distinct, higher-tier offering outside the scope of the plans covered in this listing (Free through Commerce).

Real-time automatic backups (via the same underlying technology as Jetpack VaultPress Backup) with one-click restore are included natively on Business and Commerce plans, no plugin/setup required; saved at least daily and more frequently during active editing. Lower plans (Free/Personal/Premium) rely on content revision history rather than full-site backup/restore.

Same plugin-dependent model as WordPress.org for deeper accessibility tooling; WordPress.com adds no first-party accessibility product on top.

No native multi-language content system (multiple language versions of the same page with automatic switching); WordPress.com's own guidance for multilingual sites points to either a manual approach (separate pages per language, manually linked) or third-party plugins like Polylang/WPML for a real system, both of which require Personal plan or higher for plugin installation.

Not native, but standard once a multilingual plugin (WPML, Polylang) is installed (Personal+); both provide structured translation-management workflows, identical to the WordPress.org experience since it's the same plugins.

Not native; WPML and Polylang (Personal+ plugin access) automatically generate hreflang tags and per-locale URL structures once installed, matching WordPress.org's plugin-based approach.

Native RTL (right-to-left) language support inherited from WordPress core and the block editor for languages like Arabic and Hebrew; the WordPress.com dashboard/admin interface itself is also available in RTL for supported languages.