Download version 4.6.2:

May also be accessed from a Git repository:



  • Extract the files to your site (in the web root, or choose a subdirectory). The top-level index.php should reside in this directory, as should the /textpattern/ and the /rpc/ directories.
  • Create, or establish the existence of, a working mysql database, load /textpattern/setup/index.php (or /subdir/textpattern/setup/index.php) in a browser, and follow the directions.

Detailed installation instructions


  • Log out of the admin side first.
  • Replace the three files in your main installation directory (index.php, css.php and .htaccess) and everything in your /textpattern/ and /rpc/ directories (except config.php) with the corresponding files in this distribution.
  • It is recommended that you flush the browser cache to ensure old cached files are not being used in preference to any newer versions within the upgrade.
  • When you log back in to the admin side, the relevant upgrade script is run automatically. Please take a look at your Diagnostics to view any errors and whether the correct version number is displayed.

Detailed upgrading instructions


Textpattern runs on virtually any contemporary web host you throw at it as long as the minimum system requirements are matched. Read more about Textpattern hosting here.

Latest development builds

Not for production environments. Unsupported.

If you would like to experience the latest Textpattern CMS development version, please download a Zip of the latest development build from the dev branch at GitHub and give it a spin.

Download the latest development build


For advanced users only, and not for production environments. Unsupported.

The latest development versions of Textpattern can be accessed via a Git repository:

There are various Git clients available, for multiple platforms. Tutorials for a couple popular choices can be found in the Textpattern Manual.

Pull request can be sent via Github.

What follows is a quick style guide, to be followed when modifying Textpattern source files.

Code style guide

  • Use UNIX (LF) line feeds/endings rather than Windows (CR+LF) or Mac (CR).
  • Use spaces rather than tabs.
  • Follow PSR-2 as far as possible.