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 in the blog about all the fun we had driving around a DDOS attack on our forums, how we got it back under control, and what we learned along the way. Plus PW 3.0.150 dev details and links! More
    7 February 2020
  • New post: ProcessWire core updates (January 31, 2020)— More
    31 January 2020
  • Weekly update for Jan 10, 2020—front-end file uploads in LoginRegisterPro with InputfieldFrontendFile module: More
    10 January 2020

Latest news

  • ProcessWire Weekly #301
    In the 301st issue of ProcessWire Weekly we're going to check out the latest core updates, introduce brand new third party modules RockDaterange and Modules Manager 2, and highlight a brilliant new site of the week. Read on!
    Weekly.pw / 15 February 2020
  • Driving around a DDOS attack
    Last Saturday we started getting hit with heavy traffic at the processwire.com support forums, and it soon became a full blown DDOS frenzy. This post describes all the fun, how we got it back under control, and what we learned along the way.
    Blog / 7 February 2020
  • 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