ProcessWire’s file and directory structure

An outline of ProcessWire’s file and directory structure, highlighting the locations where your site’s files go, where the core flies live, where to place modules, and more.

ProcessWire follows a simple directory structure which aims to do the following:

  • Keep your site's files and assets completely separate from ProcessWire's, so that you can upgrade your site simply by replacing ProcessWire's core.

  • Minimizes the impact to your root installation directory, so that everything is clean and doesn't create confusion with other applications you may have installed.

ProcessWire may be installed anywhere on your web server. While it's most common to install it in your web root (/) the software will run just as well under any directory structure.

ProcessWire only creates two directories from your root. This includes /wire and /site. The /wire directory contains the ProcessWire installation and modules, while the /site directory contains everything unique to a given site, including templates, your configuration, stylesheets, scripts, cache files and other assets. This structure is outlined in more detail below.

Root installation directory (/)

/.htaccessRequired directives to Apache
/index.phpBootstrap index file
/install.phpInstallation script (you should delete this after installation)

Core and modules (/wire/)

/wire/core/ProcessWire core
/wire/modules/Default plugin modules
/wire/templates-admin/Templates, stylesheets and scripts for the admin control panel

Note: To upgrade ProcessWire, you simply replace the entire /wire/ directory with that of the new version.

All files unique to a given site (/site/)

/site/config.phpYour site's configuration file
/site/assets/All writable assets including files, images, cache files, logs and temporary files created by ProcessWire.
/site/install/Installation profile. You should delete this directory after installation.
/site/modules/Any plugin modules unique to a given site (optional).
/site/templates/Template files specific to your site
/site/templates/styles/CSS files specific to your site. You may locate this directory elsewhere, and/or rename it, if you prefer.
/site/templates/scripts/Javascript files specific to your site. You may locate this directory elsewhere, and/or rename it, if you prefer.

Note: The /site/templates/ directory is the most used directory in developing a site.

Twitter updates

  • ProcessWire 3.0.161 adds support for selector operator stacking, enabling you automatically broaden searches in a single pages.find() call— More
    26 June 2020
  • ProcessWire 3.0.160 adds powerful new text-searching operators, bringing a new level of power to page-finding API calls, especially when it comes to search engine type queries. Post also includes a demo search engine where you can test it all out live— More
    19 June 2020
  • Preview of ProcessWire 3.0.160 with auto-enable of two-factor authentication, new version of TfaEmail and TfaTotp, and new selector operators coming next week. More
    12 June 2020

Latest news

  • ProcessWire Weekly #319
    In the 319th issue of ProcessWire Weekly we're going to check out the latest core updates, introduce a couple of new third party modules, and highlight the downright stunning new website of Studio Pixelgold. Read on!
    Weekly.pw / 21 June 2020
  • Powerful new text-searching abilities in 3.0.160
    In ProcessWire 3.0.160 we’ve got some major upgrades and additions to our text-search abilities. This brings a whole new level of power to $pages->find() and similar API calls, especially when it comes to search engine type queries.
    Blog / 19 June 2020
  • Subscribe to weekly ProcessWire news

“Indeed, if ProcessWire can be considered as a CMS in its own right, it also offers all the advantages of a CMF (Content Management Framework). Unlike other solutions, the programmer is not forced to follow the proposed model and can integrate his/her ways of doing things.” —Guy Verville, Spiria Digital Inc.