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

  • New post: Version 3.0.135 of ProcessWire on the dev branch focuses on some .htaccess updates, adds clarity to debug mode, and improves upon the installer— More
    5 July 2019
  • ProcessWire 3.0.133 adds a useful new Page::meta() method for a new type of page-specific persistent data storage, adds the ability for users to create their own bookmarks in Lister, and has a handy and time saving update for the asmSelect input type— More
    14 June 2019
  • New post: This week we’ll take a look at 3 different WEBP image strategies that you can use in ProcessWire 3.0.132+. Then we’ll dive into a major update for the Google Client API module, and finish up by outlining some useful new updates in FormBuilder— More
    31 May 2019

Latest news

  • ProcessWire Weekly #270
    This week in the 270th issue of ProcessWire Weekly we're going to cover the SearchEngine module, feature some recent support forum highlights, and introduce a brand new site of the week. Read on!
    Weekly.pw / 13 July 2019
  • ProcessWire 3.0.135 core updates
    Version 3.0.135 of ProcessWire on the dev branch focuses on .htaccess updates, adds additional layers of security, adds clarity to debug mode, and improves upon the installer.
    Blog / 3 July 2019
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani