Pinegrow Web Editor 10 – Oct 1, 2026

Pinegrow 10 makes existing HTML projects easier to update and deliver. Edit content in a focused workspace, continue projects across Desktop and Online, review changes visually, and publish directly from Pinegrow. Your project stays ordinary HTML, CSS and JavaScript files that you own.

Highlights

Content editing workspace

Click anything on the page and edit just its content. The Content editing workspace opens the editable fields for what you click, so there is no element tree to work through.

• Edit the fields the page exposes: text, rich HTML, images, background images, links, alternative text and page metadata.
• Manage repeatable content: add, duplicate, reorder or remove items where the component allows it.
• Searchable outline when you need it: on long pages, find content by field name or text.

The available fields depend on the page and its component definitions.

Hand routine content updates to a teammate or client: they click what they want to change and edit it, without learning the page structure. The visual editor and source stay available for the deeper work.

Read the documentation →

Desktop–Online project sync

Continue the same project in Pinegrow Desktop and Pinegrow Online.

• Connect either way: bring an Online project into Desktop, or publish a Desktop project to Online.
• Explicit sync: pull when Online has newer changes, publish when your Desktop version should become the new Online version.
• See the plan first: Pinegrow shows what will be transferred before any files move.
• Conflict review: when both copies changed, Pinegrow reports the conflict so you can compare versions before choosing one. Online revisions give you another recovery point.

Work from the office machine, a laptop or a browser, and decide each time which version continues, instead of copying folders by hand.

Read the documentation →

Visual change review

See what a revision changed on the page before you restore it.

• Source comparison of changed files.
• Rendered before-and-after pages side by side.
• Step through changed elements: every added, modified and removed element.
• Restore selectively: individual files or a complete earlier revision. Before a full restore, Pinegrow saves a safety revision so you can return to your newer work.

Judge a change by what it does to the page, not only by a code diff, and roll back only the files you mean to.

Read the documentation →

Publish to GitHub, Netlify, Cloudflare Pages and SFTP

Publish complete projects without leaving Pinegrow. A preflight review lists the files to upload, remote files that can be removed, excluded files and warnings before anything is deployed.

• GitHub: choose the repository, branch and folder, and add a commit message.
• Netlify: connect a new or existing site, then publish a production or preview deploy.
• Cloudflare Pages: publish to a Pages project in your Cloudflare account.
• SFTP: connect with a password or private key, with explicit server-fingerprint verification.
• Only changed files: after the first publish, Pinegrow transfers just what changed.

SFTP publishing is available in Pinegrow Desktop. Pinegrow Online publishes to GitHub, Netlify and Cloudflare Pages.

Go from edited page to live site in one reviewed step, and see every upload and deletion before your server changes.

Read the documentation →

More improvements

Spell Check

Find and fix spelling mistakes in selected content, the current page or all open pages.

• Checks what is easy to miss: alternative text, titles, labels and placeholders, not only visible text.
• Your own dictionaries: add product names and technical terms to a project or global dictionary, or ignore a spelling that is correct in context.
• Languages: English is included; German, Italian and Spanish dictionaries can be downloaded.
• AI help: send an issue to AI Assistant when a fix needs more than a dictionary word.

Catch the typo in an image description or form placeholder before a visitor does.

Read the documentation →

Page Health

Find HTML problems that are hard to spot by eye.

• Malformed structure and incorrect nesting.
• Missing document essentials.
• Duplicate IDs and broken references from labels, ARIA attributes and in-page links.
• Fix it your way: apply a direct fix where available, or ask AI Assistant to resolve one issue or a whole group. Every fix can be undone.

Find the broken label or duplicate ID before it becomes a confusing bug report.

Read the documentation →

Accessibility checks

Check the rendered page with the axe accessibility engine, using WCAG 2.2 AA rules and optional best-practice checks.

• Any scope: a selection, a page or all open pages, including responsive views.
• Prioritize: filter by impact, with repeated results grouped together.
• Fix: guided fixes for common issues, or AI Assistant repairs in the context of the page.
• Human judgment included: optionally list the items that need manual review.

Automated checks are a first pass: keyboard testing, screen-reader testing and human review are still needed.

Catch common accessibility problems while you build, not after launch.

Read the documentation →

SVG controls

Work with inline SVG graphics as project content.

• Preview, view or replace an SVG’s complete source.
• Browse and search the SVG files and inline graphics already used in your project’s editable pages.
• Safe by default: previews are sanitized, and scripts and unsafe external content are rejected.

Reuse the icons you already have instead of hunting through files and copying markup by hand.

Read the documentation →

Protected credentials and Pinegrow Data

Available in Pinegrow Desktop.

• Credentials: API keys and connection credentials are stored in your operating system’s credential store.
• Pinegrow Data folder: settings, recent files, recovery data, snapshots, AI Assistant data and thumbnails now live outside Pinegrow’s Chromium profile, so clearing or recreating that profile no longer removes them.
• Automatic migration when you upgrade. You can reveal or move the Pinegrow Data folder.

Your keys stay out of ordinary settings files, and your snapshots and recovery data survive a browser-profile reset.

Read the documentation →

AI Assistant

Review AI changes

Decide what to keep after an AI task. With review turned on, Pinegrow records the project before the task and compares it with the result.

• Same tools as revision review: source comparison, rendered before-and-after and a step-through of changed elements.
• Your choice: keep the whole result, continue editing, restore selected files or revert the complete task.
• Safety snapshot: saved before a whole-task revert.

Let AI make broad changes, and still approve what goes into your project.

Read the documentation →

Improved Codex integration

Codex is now a full AI Assistant provider in Pinegrow Desktop.

• Sign in with Codex instead of setting up a separate OpenAI API key.
• Your models: choose from the models and reasoning options available to your account.
• Longer tasks: resume or steer a task without losing its context.
• Edits go through Pinegrow: changes are validated, shown in the live preview, and included in undo and optional visual review.

Use the Codex access you already have, with every change visible in Pinegrow and undoable.

Read the documentation →

MCP server

Connect an external AI assistant to Pinegrow Desktop through its local MCP server.

• The assistant can inspect pages and styles in the live editor and make changes through Pinegrow’s editing tools.
• Setup: turn on external access in Pinegrow, then add the connection details and access token it provides to your assistant. Keep the token private.

Keep using the AI assistant you prefer, and watch its edits appear in Pinegrow’s live preview.

Read the documentation →

WebMCP for AI agents

In Pinegrow Online, AI agents running in browsers that support WebMCP can inspect and edit pages and CSS through Pinegrow’s editing tools, instead of changing the files directly.

Bring your own browser-based AI agent to an Online project and keep its edits inside Pinegrow’s editor.

Read the documentation →

AI CSS editing

AI Assistant now understands the CSS cascade.

• Inspects the cascade and computed styles of an element, including states such as hover and focus.
• Edits the right source: a CSS, Sass or Less file, a style block or an inline declaration.
• Safe edits: changes go through Pinegrow’s live stylesheet model with validation, preview and undo. Framework-managed and generated styles stay protected.

Ask for a style change and get an edit in the stylesheet where it belongs, not another override.

Read the documentation →

Choose the generated project framework

Pick Tailwind CSS 4, Bootstrap 5 or plain HTML and CSS before AI Assistant creates a new site.

• Pinegrow creates the matching starter project.
• The AI is told to use that framework.
• The matching visual styling tools are turned on.

Start with the framework you actually want instead of converting a generated site afterwards.

Read the documentation →

Local voice transcription

Speak your AI Assistant prompts in Pinegrow Desktop, with transcription running on your computer.

• Private: a downloadable Whisper model transcribes locally. No speech-to-text API is needed, and the recording is not sent to your AI provider; only the transcribed text is sent, as a normal prompt.
• Choose a model that balances download size, speed and accuracy, or use a compatible custom GGUF model.

Dictate long instructions, and keep the recording on your own machine.

Read the documentation →

Bug fixes

Polish and fixes

Bug fixes and reliability improvements across the app.