ProcessWire for publishers: a flexible PHP CMS with a strong API

What is ProcessWire?

ProcessWire is a PHP content management system whose repository lists Ryan Cramer / Ryan Cramer Design, LLC as copyright holder. The repository describes ProcessWire 3.x as a friendly and powerful open source CMS with a strong API. According to the project’s background page, it was released as open source in October 2010, having evolved from Dictator CMS (2003) and ProcessWire 1.0 (2006), neither of which was open source.

Its model is fields and templates: you define the fields an article needs, group them into templates, and build pages from them. The strong API the repository mentions is a PHP API for working with those pages in templates and code.

Who is ProcessWire best for?

ProcessWire is a good match for publishers with a PHP developer who want free software and an editing interface designed around their own content types: a magazine with articles, columns, issues and authors, for example. Role-based access by template suits organisations with several desks.

It is less suitable for teams wanting a large marketplace of themes and plugins, for publishers without a developer, and for anyone who needs vendor-backed hosting or support. Compare with other options in the CMS directory.

Consider a monthly magazine with issues, articles, columnists and sponsored sections. In ProcessWire a developer can model each as a template with its own fields and give each desk its own role, so the editing screen for a columnist differs from the one for a sponsored feature. A site that is only a blog gains little from that flexibility.

The honest question is developer availability. ProcessWire’s strength is that a developer can shape it closely, and its weakness is that someone must.

Editorial workflow

Access control follows a clear chain. Users are assigned to one or more roles, roles are given permissions and roles are assigned to templates, which controls who can reach which pages. In a newsroom this lets you give a features desk and a news desk different access to different article types.

The documentation pages we opened do not describe drafts, revisions, scheduling or a review workflow, so we make no claims about them. If your editors rely on those, test them in a trial install or ask in the project’s community before committing. Our feature checklist lists what to check.

SEO, structured data and feeds

We could not verify built-in sitemaps, structured data or feeds from the pages we opened. The module directory lists SeoNeo, described as a modern SEO coordinator that uses native ProcessWire fields for meta, robots and canonical, and a module for managing custom-path redirects.

Because ProcessWire templates are PHP, a developer controls the HTML and can output whatever structured data is needed. Follow Google’s documentation, not module descriptions, and check any module’s current maintenance.

Media, multilingual and performance

Multi-language support is built into the project, according to the documentation. Multi-language page names (URLs) and multi-language text fields are provided by the Language Support, Language Support Fields and Language Support Page Names modules, which you install from the admin. A gettext-style translation system for interface text is also described.

The pages we opened did not cover image processing beyond the GD or ImageMagick requirement, or caching. We make no performance claims.

Hosting and requirements

The installation page says PHP 8.x is recommended and PHP 7.1 and newer are supported. It lists MySQL 5.6 or newer (or equivalent MariaDB), Apache with mod_rewrite enabled and .htaccess support, PHP’s GD 2 or ImageMagick, and PDO database support.

Those numbers look dated beside current PHP and MySQL releases, so confirm them against the current install guide and your host before relying on them. Apache is the documented web server; we have not verified other servers. The self-hosted guide covers the work of running one.

Extending ProcessWire

The module directory listed 712 modules on 2026-10-10. That is modest next to the largest ecosystems, though many projects need less when templates are flexible. The strong PHP API means developers can write their own modules and templates.

We have not verified how quickly modules follow core updates or how many are actively maintained, and we did not review any ProcessWire API for decoupled use; see the headless section for general guidance.

What does ProcessWire cost?

The software is free. The licence is the Mozilla Public License 2.0, and the project says your own original code and files need not use the same licence. See our licensing guide for how that compares with GPL and commercial licences.

The costs are hosting and development, which for ProcessWire means PHP developer time, since the editing interface and templates are built to your content model. We did not verify any paid modules or support plans. Our cost guide lists the other lines to budget.

Because the licence is free and the module directory is modest, the budget concentrates in build time. A publisher should ask a developer to quote the template and field model, the editing screens, the multi-language setup if needed, and the SEO output, since those are the items other systems often supply as plugins.

Where does ProcessWire fall short?

• Smaller ecosystem. 712 modules in the directory is far fewer than the largest systems offer.
• Workflow features unverified. Drafts, revisions and scheduling are not described in the pages we opened.
• Developer-built. The editorial experience depends on how well the site is built.
• No GitHub Releases. Versions are tags, so release notes and update checks take more effort.
• Documented stack looks dated. The listed minimum PHP and MySQL versions are old; check current guidance.

The verdict for publishers

ProcessWire is a strong choice for a publication with a developer and a distinctive content structure: a flexible model, role access by template and multi-language support at no licence cost. The MPL licence is friendly to commercial work.

It is a harder sell for a team that wants a ready-made newsroom product with plugins for everything. This profile is drawn from the project’s own documentation, not a test install; see how we test.