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

  • Happy New Year! Today I’ve bumped the version on the dev branch to 3.0.170, and it’s quite a lot of updates. This post covers most of them. In this post, there’s also a question for you: what would you like to see in ProcessWire in 2021? More
    1 January 2021
  • In this week’s blog post we’ll take a brief look at a powerful new ProFields module for ProcessWire that’s just around the corner—the Combo field: More
    4 December 2020
  • There’s a new modules directory on the ProcessWire site now up and running. In this post we’ll cover a few details about what’s changed and what’s new—More
    20 November 2020

Latest news

  • ProcessWire Weekly #347
    In the 347th issue of ProcessWire Weekly we'll check out ProcessWire 3.0.170, introduce the PDF Fieldtype/Inputfield module, and more. Read on!
    Weekly.pw / 2 January 2021
  • ProcessWire 3.0.170 core updates
    Happy New Year! Today I’ve bumped the version on the dev branch to 3.0.170, and it’s quite a lot of updates. This post covers most of them. In this post, there’s also a question for you: what would you like to see in ProcessWire in 2021?
    Blog / 1 January 2021
  • Subscribe to weekly ProcessWire news

“To Drupal, or to ProcessWire? The million dollar choice. We decided to make an early switch to PW. And in retrospect, ProcessWire was probably the best decision we made. Thanks are due to ProcessWire and the amazing system and set of modules that are in place.” —Unni Krishnan, Founder of PigtailPundits