Kerf vs. Pinegrow.
Pinegrow has been the serious developer's visual web builder for over a decade. Kerf is a newer, more focused tool — same broad goal of editing the rendered page directly, but a smaller surface area built around click-to-source sync. The right pick depends on how much builder you want.
At a glance
Both Kerf and Pinegrow give you:
- Visual editing of HTML and CSS — direct manipulation, code-aware.
- Live preview — see your changes as you make them.
- Source-file output — your edits land in your actual project files.
- Framework awareness — both understand Tailwind and Bootstrap.
The difference is breadth. Pinegrow ships a full builder — component library, template actions, WordPress export, master pages. Kerf is a focused editor: fewer panels and a more direct click-to-source path.
Kerf is better for
- Editing existing sites without a learning curve. Kerf's surface is small on purpose: a code pane, a preview, a layers panel, a properties panel. Open a folder and start working — there's no project setup, no master-page concept, no library config.
- Exact click-to-source. Click any element and Kerf opens the exact line in Monaco. Pinegrow has element-level selection but doesn't push you all the way to the source line in the same way.
- Lower price. Kerf is free for the core editor, $96/year or $10/mo for Pro. Pinegrow Pro is around $99 (one-time or yearly) with an upgrade path for WordPress and Tailwind add-ons.
- Modern editor under the hood. Kerf uses Monaco, the editor engine from VS Code, with autocomplete and multi-cursor editing. Pinegrow's built-in code editor is solid but lighter.
- Static-site shipping. Kerf Pro deploys directly to Vercel from inside the editor. Pinegrow has FTP and live publishing but no Vercel-specific integration.
Pinegrow is better for
- Building from scratch with a component library. Pinegrow's Bootstrap and Tailwind blocks let you drag in pre-built sections — heroes, navs, footers, pricing tables. Kerf doesn't have a component library; it edits what's there.
- WordPress theme development. Pinegrow's WordPress add-on turns a static HTML mockup into a working WordPress theme with PHP templates. Kerf doesn't do PHP or WordPress export.
- Master pages and template actions. Pinegrow lets you define a master layout and propagate changes across pages. Kerf treats each file as standalone (snippets, in Pro, are the closest equivalent).
- Deeper feature surface. Pinegrow has CSS Grid editor panels, breakpoint management, animation tools, and a long list of accumulated features.
- Established track record. Pinegrow has been in active development since 2014. Kerf is newer.
Feature comparison
| Feature | Kerf | Pinegrow |
|---|---|---|
| Click-to-source sync | Bidirectional, exact line | Element selection |
| Editor engine | Monaco (VS Code engine) | Built-in code editor |
| Component library | Snippets (Pro) | Extensive Bootstrap + Tailwind blocks |
| WordPress theme export | — | Yes (add-on) |
| Master pages / template inheritance | — | Yes |
| Framework support | Tailwind, Bootstrap (auto-detected) | Tailwind + Bootstrap builders |
| Design token consolidation | Yes (Pro) | Manual |
| Accessibility audit | 5-category audit (Pro) | Inline checks |
| Deploy | One-click Vercel (Pro) | FTP, live publish |
| Pricing | Free / $96 yr / $10 mo / $149 once | One-time or ~$99/yr |
Pricing
Kerf
- Free tier: full visual editor.
- Pro: $96/year, $10/mo, or $149 lifetime.
- Pro adds Vercel deploy, snippets, design token consolidation, an accessibility audit, and a React Native editor.
Pinegrow
- Pro: ~$99 — one-time (1 yr of updates) or yearly subscription.
- Add-ons (WordPress, Tailwind) priced separately.
- No free tier — paid only.
- Verify current pricing at pinegrow.com/buy.
Which one to pick
Pick Pinegrow if you want a full builder — pre-built component blocks, WordPress theme export, master pages, deep CSS Grid tooling. Its depth pays off when you're constructing sites from a library of pieces or shipping WordPress themes.
Pick Kerf to edit HTML and CSS you already have — visual editing, with the changes landing in your files. If you're maintaining a static site rather than building one from blocks, Kerf is the lighter fit.