ProcessWire

Last reviewed Sep 13, 2026 · 792 words

Everything in ProcessWire is a page, every page has a template, and a template is nothing more than the list of fields you decided it should have. Once that clicks, the rest of the system is one API call: $pages->find("template=product, price<50, sort=-modified, limit=12") returns exactly what it says, and you loop over it in a plain PHP template file. That is the whole pitch, and it is why ProcessWire has kept a devoted developer following for 16 years at a star count that undersells it.

No content type is built in, so none is in your way

WordPress gives you posts and pages and makes you fight custom post types into shape. ProcessWire gives you a blank field library: text, textarea, integer, float, date, image, file, page reference, repeater, options, and more, each with its own validation and input widget. You compose templates from those fields in the admin, then write a template file that outputs them. A recipe site, a product catalogue, a documentary archive with 30 metadata fields per item: all of them are just templates. There is no shortcode layer, no theme framework, and the front-end markup is whatever you write, which is why ProcessWire sites tend to score well on performance audits without effort.

The API is the reason developers stay

Selectors (that template=product, price<50 syntax) work everywhere: finding pages, filtering repeaters, querying users, even matching form input. Pages know their parent, children, and siblings. Fields know how to render themselves. Hooks let you attach behaviour to almost any method in the core without editing it, which keeps upgrades painless. The learning curve is short for anyone who has written PHP, the documentation on processwire.com is unusually thorough, and the forum, while small, is where the lead developer answers questions personally. The CMS category is full of systems that promise this flexibility; ProcessWire is the one that ships with an admin a client can use.

Editors get a functional admin, not a beautiful one

The catalogue's "less polished for non-developers" is accurate. The admin is clean, fast, and consistent, but it is generic by design: a tree of pages, an edit form generated from the template's fields, and not much guidance. There is no block editor, no live preview by default, no drag-and-drop page builder. Editors who came from WordPress or Squarespace will find it plain; editors who came from spreadsheets will find it obvious. If a rich editing experience is the deciding factor, Kirby and Craft CMS invest far more there, and both charge a licence for the privilege. ProcessWire's admin is free, MPL-2.0 licensed, and does the job.

Hosting is any PHP box, and the paid modules are optional

Requirements are PHP with the usual extensions, MySQL or MariaDB, and Apache with mod_rewrite (Nginx works with a few rewrite rules). 256 MB of RAM is ample; ProcessWire is light. Install by unzipping the release, browsing to the installer, and picking a site profile (blank, or a demo). Updates are a matter of replacing the wire directory; your site lives in site and is never touched. The module directory has hundreds of free modules, and the lead developer sells a handful of Pro modules (a form builder, page caching, advanced fields) that fund the project. You can run a serious site without any of them.

Where it is the wrong pick

Three cases. You want a site an editor can restyle without a developer: no. You want a large plugin ecosystem for things like e-commerce or memberships: WordPress has a thousand options where ProcessWire has a few community efforts. You want a headless CMS with a first-class GraphQL or REST layer: ProcessWire can expose JSON from a template file in ten lines, and there are modules for GraphQL, but it is a server-rendered system at heart and the headless tooling is thinner than dedicated options. Its community is small, and that shows most when you hit an unusual integration and find one old forum thread and nothing else.

What I'd do

For any content site where I am the developer and the content model is not "posts and pages", ProcessWire is my default over WordPress: I define the templates, write the fields into markup I control, add page caching, and hand the client an admin that will not break. I pair it with MariaDB on a 256 MB PHP host and skip the Pro modules until a client asks for the form builder. For a client who expects to redesign pages themselves, I steer them to a page-builder CMS and save us both the conversation.