Pinegrow Web Editor is a desktop application for building and maintaining websites on Windows, macOS and Linux. It combines visual page editing with direct access to HTML and CSS, so the layout on screen and the underlying files remain part of the same workflow. You can open an existing HTML site, begin with a template or create a project from scratch.
Editing HTML visually or in code
The visual editor works on page elements: you can insert them, move them into a different container, clone them or remove them. Multiple selection lets you change several elements together, while the repeater creates multiple copies. Element-level and whole-page code editors provide access to markup when a change is easier to express in HTML.
Pinegrow works with ordinary website files. Its Project panel displays the contents of a project folder, where you can open pages and manage files. Changes made through another code editor can appear in the page preview, allowing visual editing and external coding to share the same project.
Responsive styling
Selecting an element exposes the CSS rules that style it in the CSS Tree. Visual controls and code editing work together, so you can adjust a property through the interface or edit the rule itself. Pinegrow also handles CSS variables and live Sass and Less editing, with a separate visual editor for CSS Grid layouts.
Several page views can show the same design at different widths. Device presets, rotation and manual resizing help examine how content flows between screen sizes. Pinegrow detects breakpoints in the stylesheets, and you can create additional media-query rules from the Style panel rather than maintaining a separate mobile page.
Tailwind CSS and Bootstrap
For Tailwind CSS projects, visual controls apply utilities to selected elements. The Class Inspector exposes the classes already in use, while reusable styles collect combinations that belong together. Custom themes and responsive or state variants allow these controls to work within a project’s own design choices.
Bootstrap editing centers on its components and grid. You can insert ready-made components, resize columns on the page and adjust the theme through the Design panel. Dynamic elements such as modals remain available while editing, so their contents can be worked on within the design.
Reusing markup across pages
Pinegrow components turn page elements into reusable pieces. A component can define editable content, attributes or classes, allowing each instance to vary in selected places while retaining a shared structure. Updating the component can then update its copies throughout the project.
Master pages handle shared page structure, including navigation, headers and footers. Content pages retain their own editable areas within that structure. Partial HTML files can also be edited in the context of their parent page, and one project can supply a reusable component library to another.
Content fields
The Content Workspace presents a page’s words, images, links and page information as fields beside the live preview. Selecting an item on the page opens its fields for editing. Styled headings are divided into text parts so their spans, icons and line breaks can remain intact while the wording changes.
Image fields expose the source and alternative text, with crop and resize operations that save a new image. Link fields provide a helper for web addresses, email, telephone links and page anchors. Form labels, placeholders, button captions, page titles and meta descriptions can also be updated through this workspace.
Client access in CMS Mode
For client editing, Pinegrow lets the designer name and group fields and choose which are available in CMS Mode. Fields begin as author-only; opening selected fields to editors gives them access to content without exposing every layout control. A test mode shows the editing permissions before handing over the project.
WordPress export
The optional WordPress Builder converts HTML designs into WordPress themes, custom blocks and plugins. Assigning WordPress actions to page elements connects the design to functions such as dynamic content. Live content from a WordPress site can appear during development, and the resulting theme or plugin is exported as native WordPress files that run independently of Pinegrow.
Both classic and block themes are supported. The separate Shop Builder for WooCommerce extends the WordPress tools with store actions and requires WordPress Builder. This shop extension is available through subscription rather than the one-time editor license.
Pinegrow Interactions
Pinegrow Interactions combines an event, a target element and an animation. Hover or click events can start a preset animation, or you can build the motion in a timeline by adjusting keyframes and properties such as transforms and colors. Scroll scenes can follow scrolling continuously or start when an element reaches a chosen position.
The animations use GSAP, and edits appear in the page view while the timeline is being adjusted. Interactions requires a subscription; it is not included in the one-time license’s permanent feature set.
AI Assistant and project revisions
The built-in AI Assistant can alter selected markup, change styling, generate page content or turn a design image into HTML. Its requests use the selected element and project context, including the framework in use. Image generation and design variations are also available, using Pinegrow AI credits or a configured provider API key.
Changes can be reviewed visually before keeping the result. Project revisions provide another level of control: compare two saved states, inspect changed elements and restore a complete revision or selected parts. Automatic revisions can preserve restore points during ordinary saves as well as larger edits.
Site publishing
Pinegrow Web Editor publishes projects to GitHub, Netlify, Cloudflare Pages or an SFTP server. Before transfer, a review lists files to upload, exclusions and potential remote deletions. Later publishes send changed files, while Netlify and Cloudflare Pages also support separate preview deployments for checking a change before it reaches the live site.
Spelling, HTML, accessibility and broken-link checks help inspect the project before publishing. The editor also provides sitemap tools. Publishing to Netlify or Cloudflare Pages transfers static files; server functions need a different deployment workflow.
