Webflow vs Framer vs hand-coded: when to pick what.

This question comes up in roughly half our discovery calls. It used to have a clean answer. In 2026 it doesn't — the tools have all matured in different directions, and the decision is now genuinely contextual. This essay is the framework we use to decide, project by project.

We ship in all three. We're not loyal to any. What follows is honest, not promotional.

The decision framework, in one paragraph

The choice depends on three variables: how much custom interaction the design needs, who will maintain the site after launch, and how much content will be added over time. Each tool optimizes for a different combination of those three. Pick the one whose optimum matches your project.

The rest of this post unpacks that paragraph.

Webflow: when it wins

Webflow is the best in this class when you have:

• A marketing site with moderate-to-rich design (custom layouts, hover interactions, scroll animations)
• A team that includes at least one non-developer who needs to update content
• A roadmap that involves adding pages and blog posts over time
• A budget that allows for Webflow's CMS hosting (~$300–400/year for the Business plan)

Webflow's strength is the gap between "design fidelity" and "content editor accessibility." A marketer can update a case study without breaking the page. A designer can add custom interactions without writing CSS. The CMS is genuinely usable.

Where Webflow is painful

It struggles when:

• You need real backend logic (auth, complex forms, data processing). Webflow's "Logic" feature exists but is brittle for anything non-trivial.
• The site needs to scale past ~1,000 CMS items per collection. Performance degrades, build times grow.
• You want full source control with proper git workflows. Webflow's export is fine but it's a snapshot, not a sync.
• The site needs to integrate deeply with a third-party stack (a custom API, an internal data source). Webflow's integrations are mid-tier.

The Webflow ceiling is real. Hit it and you're rebuilding.

Framer: when it wins

Framer is the best when you have:

• A landing page or early-stage marketing site where you want exceptional animation and motion design
• A team where the designer is the developer (or close to it)
• A timeline measured in days, not weeks
• Less complex CMS needs

Framer's strength is the gap between "Figma fidelity" and "shipped page." The visual layer translates almost 1:1 from Figma. Animations are first-class. The new Framer of 2025–2026 is genuinely close to a "code-output-equivalent" tool for visual work.

Where Framer is painful

It struggles when:

• The site has more than ~30 unique page types or deep content hierarchies
• You need traditional SEO controls at the depth Webflow offers (Webflow's SEO surface is still better, page by page)
• The team has multiple non-designer collaborators editing content — Framer's CMS is leaner than Webflow's
• You expect to leave Framer. Exporting Framer to anything else is significantly harder than Webflow export. You're more locked in.

Framer is a launching tool, not always a maintaining tool. It's exceptional for the first six months and can become a constraint at month eighteen.

Hand-coded: when it's worth the cost

Hand-coded (a modern stack — Next.js, Astro, SvelteKit, plus a headless CMS like Sanity or Contentful) wins when:

• The site has bespoke interaction requirements — true product surfaces, multi-step flows, custom data visualizations
• The team has developer capacity to maintain it
• You're at a scale where the time investment pays back — typically 100+ pages, or sites with significant traffic
• You need deep integration with internal systems, custom APIs, or analytics infrastructure
• Performance is a feature — every kilobyte matters, and the page must score 99 on Lighthouse

The strength of hand-coded is no ceilings. Anything you can imagine, you can build. The price is that you have to imagine it, build it, and maintain it.

Where hand-coded is painful

It struggles when:

• The team has no developer, or only contractor capacity. Hand-coded sites die slow deaths when the contractor leaves.
• The content cadence is high and managed by non-developers. Headless CMS interfaces have come a long way but they're still worse for non-tech writers than Webflow's editor.
• The project is time-boxed under three weeks and the design is moderate. You'd pay 3x the cost for Webflow-equivalent output.

The honest comparison: a hand-coded site is better than Webflow on every axis that matters once you cross a complexity threshold. Below that threshold, it's worse on every axis except long-term flexibility.

Hand-coded is better on every axis once you cross a complexity threshold. Below it, it's worse on every axis except long-term flexibility. — Internal stack decision note

The hybrid approach we now default to

For most projects we run in 2026, the answer is none of the above as a single tool — it's a hybrid:

• Marketing site: Webflow (best balance of fidelity, editor access, and SEO)
• Application UI: Hand-coded (real product, real data, real flexibility)
• Launch landing pages and microsites: Framer (speed and motion design)
• Blog system: Hand-coded with a CMS (this site is built this way — Eleventy + Sveltia CMS)

The hybrid frustrates founders who want a single answer. It's also what produces sites that don't compromise.

The comparison, on one screen

Everything above, condensed. Read down the column you're leaning toward and check whether the "costs you" row is a price you're willing to pay — that's usually the row that decides it.

The row that catches most teams out is the third one. A tool that a marketer can update on a Friday afternoon is worth a real amount of money, and that value never shows up in a feature comparison.

Decision flowchart

If you want a single rule:

• Is the site product UI? → Hand-coded.
• Is it a launching landing page or microsite with rich animation needs? → Framer.
• Is it a marketing site that non-developers need to edit? → Webflow.
• Is it a content site with high publishing cadence? → Hand-coded with a CMS (Eleventy/Astro + Sveltia/Sanity).
• Is it a single-page promo that needs to ship this week? → Framer.

The flowchart breaks at the edges. A site that's "mostly marketing but with one custom data widget" is exactly the kind of project where the wrong tool choice produces months of regret. For those, run the three-variable test — interaction complexity, maintainer profile, content cadence — and pick honestly.

What we're watching in 2026

A few moving targets that may change this comparison in the next year:

• Framer's CMS is improving fast and may close the gap with Webflow for content-heavy sites.
• Webflow's developer tools (more meaningful code export, real API integrations) are slowly maturing.
• AI-augmented hand-coded stacks are eating into the "Webflow saves time" argument — at some point, the speed advantage of Webflow disappears when AI can scaffold the equivalent in a hand-coded framework in minutes.

We re-run this comparison every six months and the answer shifts. For now, the hybrid approach above is what we default to. In a year, the right answer may be different.

The tool isn't the brand. Pick the one that fits the project, and don't get attached.