I build on all three of these every month, which means I have no reason to sell you one of them. What follows is how I'd choose if it were my own business, including the cases where the popular answer is wrong.
Feature-checklist comparisons are useless here, because all three can produce a good-looking website. What separates them is what they cost you a year later, when the agency is gone and someone in your office needs to add a page.
The question people ask is the wrong one
"Which platform is best?" has no answer. The question that does have an answer is: which platform's weaknesses can you live with? Every one of these three is strong in its centre and awkward at its edges, and projects go wrong when a business spends two years fighting the edge.
A second question worth asking early: who maintains this in eighteen months? The honest answer changes the recommendation more than any feature does.
WordPress: the one that can do anything
WordPress runs a large share of the web for a reason: whatever you need, someone has built it. Memberships, bookings, multilingual content, learning platforms, directories, a shop bolted onto a content site — all solved, all available, usually several times over.
Where it's genuinely the best answer:
- Content-heavy sites: blogs, magazines, sites with hundreds of pages.
- Anything with unusual functionality, or functionality that will grow in directions you can't predict.
- Multilingual sites — nothing else in this comparison handles two languages as cheaply.
- Businesses that want full ownership: your host, your database, your files, exportable and movable.
- Tight budgets that still need real capability.
What it costs you: maintenance is not optional. Core, theme and plugin updates, backups, security monitoring, and the occasional afternoon when two plugins disagree. That's a real recurring cost in money or attention, and it's the thing people underestimate. The flexibility that makes WordPress powerful is the same flexibility that lets a site accumulate thirty plugins and become slow.
The other cost is that quality varies enormously. "Built in WordPress" describes both a fast, clean, custom site and a bloated multipurpose theme with a page builder stacked on top. Same label, completely different asset.
Shopify: the one that sells
Shopify is not a website builder that happens to have a cart. It's ecommerce infrastructure — inventory, variants, payments, taxes, shipping rates, abandoned checkouts, discount logic, fraud analysis — with a website attached. That distinction is the whole argument.
Where it's genuinely the best answer:
- Any store that's the main business rather than a sideline.
- Catalogs past roughly fifty products, or any catalog with real variant complexity.
- Selling in several currencies or countries.
- Teams who need to process orders daily without a developer nearby.
- Anyone who does not want to be responsible for the security of a payment flow.
What it costs you: a monthly fee plus transaction costs, and an app ecosystem that quietly becomes a second subscription bill — five apps at fifteen to thirty a month is normal and adds up faster than people expect. Checkout is only customisable on the Plus plan. And content management is the weak spot: the blog is basic, and building a large non-product content section on Shopify is working against the tool.
Webflow: the one that looks exactly right
Webflow is a visual development environment. A developer builds with the real box model, flexbox and grid, and Webflow outputs clean code with hosting and a CMS included. It gives you the design precision of hand-coding with an editor a marketer can use.
Where it's genuinely the best answer:
- Design-forward marketing sites where the look carries the value.
- Figma designs that must be built exactly, not approximately.
- Businesses that want zero maintenance: no updates, no plugins, no server.
- Marketing teams that publish regularly and must not be able to break the layout.
- Fast, animation-heavy sites where performance still matters.
What it costs you: hosting is per-site and more expensive than shared WordPress hosting. CMS collections have item limits that a large content site will hit. Ecommerce is fine for a small catalog and wrong for a real store. Multilingual support exists but is priced as an add-on. And the pool of developers who can pick up an existing Webflow project is smaller than the WordPress pool — worth weighing if you like knowing you can replace your developer easily.
Not sure which one your project needs? Tell me what the site has to do and who maintains it afterwards, and I'll tell you which of the three I'd use — including when the answer is "none of them, keep what you have."
Side by side
| WordPress | Shopify | Webflow | |
|---|---|---|---|
| Best at | Content & custom functionality | Selling products | Design-led marketing sites |
| Maintenance | Ongoing, unavoidable | Handled by Shopify | Handled by Webflow |
| Ecommerce | Strong via WooCommerce | Best in class | Small catalogs only |
| Multilingual | Mature, inexpensive | Workable | Paid add-on |
| Editing by non-developers | Good with a page builder | Excellent for products | Excellent, hard to break |
| You own | Everything, portable | Your data, not the platform | Your data, exportable code |
| Developer pool | Enormous | Large | Smaller |
Scroll the table sideways on a phone.
How I'd choose, case by case
A local service business — clinic, trades, law firm, agency. WordPress, almost always. You'll want service pages, a blog for local search, forms, and probably a second language eventually. Webflow if the brand is the differentiator and nobody internally will maintain anything.
A shop that is the business. Shopify. Not because WooCommerce can't do it, but because the operational side — orders, inventory, refunds, taxes — is where you'll spend your time, and that's where Shopify is years ahead.
A content site with a handful of products. WordPress with WooCommerce. The content is the main asset; the shop is a feature of it. Splitting across two platforms costs more than it saves at this size.
A funded startup with a designer and a marketing team. Webflow. The design gets built exactly, the marketers publish without engineering time, and nobody has to own a server.
A campaign or launch page. Whatever your main site already runs, so the page inherits your domain, analytics and forms. Standalone campaigns are the exception, and Webflow is quickest there.
A membership site, course platform or booking system. WordPress. It's the only one of the three where this is a solved problem rather than a project.
The year-two costs nobody quotes
Build price is the number everyone compares. The number that actually differs is what happens after:
- WordPress: hosting, plus maintenance in money or your own time, plus premium plugin renewals. Cheapest to start, most attention to keep.
- Shopify: platform fee, transaction fees, and app subscriptions that grow with ambition. Predictable, but it never goes down.
- Webflow: per-site hosting, higher than shared hosting but with maintenance included. The flattest curve of the three.
Add the cost of change. On WordPress, small changes are cheap and there's always someone who can do them. On Webflow, changes are quick but the pool of people is smaller. On Shopify, product and content changes are trivial and deep theme changes need a developer who writes Liquid.
Switching later
It's not a life sentence, but it's not free either. Content migrates reasonably well in every direction. What doesn't migrate is the design, the custom functionality and — if you're careless — your search rankings.
The rankings part is entirely within your control: a complete map of old URLs to new ones, 301 redirects in place on launch day, and checking Search Console for the following month. Sites that lose traffic in a replatform lose it because nobody did this, not because the platform changed.
FAQ
Is WordPress still worth using?
Yes, and the criticism usually aimed at it is really aimed at bad WordPress: a multipurpose theme, a page builder on top and thirty plugins. Built deliberately, with few plugins and clean code, it's fast, flexible and the most portable of the three. It just demands more discipline than platforms that make the decisions for you.
Can Webflow replace WordPress?
For marketing sites, often yes. For anything needing memberships, bookings, complex multilingual content or a large catalog, no — you'd spend the saved maintenance effort working around missing capability. Webflow's CMS is excellent at what it does and deliberately narrower than WordPress.
Is Shopify worth it for a small catalog?
If selling is the main activity, yes, even with ten products — you're paying for the checkout, the payment handling and the operational tools, not the page count. If you have five products alongside a content business, WooCommerce or Webflow Ecommerce is the cheaper fit.
Which platform is best for SEO?
All three can rank. Google doesn't care what built the page; it cares about speed, structure, content and links. WordPress gives you the finest control over technical SEO and the best blogging tools, which is why content-led strategies tend to land there. That is an advantage of the tooling, not of the platform's ranking ability.
The short version
Selling products as your main business: Shopify. Content, complex functionality or a second language: WordPress. A design-led marketing site with nobody to maintain it: Webflow. And if you're torn between two of them, decide by asking who will be editing the site in eighteen months — that answer is usually the tiebreaker.
Want a second opinion on a platform decision? I build on all three, so I have no stake in the answer. Tell me the project and I'll tell you what I'd use and why.