File (Field) Paths

Open Bugs: 
Development Status: 
Seeking co-maintainer(s)
Under active development

The File (Field) Paths module extends the default functionality of Drupal's core Upload module, the FileField module and many other File Upload modules by adding the ability to use node tokens in destination paths and filenames.

In simple terms, File (Field) Paths allows you to automatically sort and rename your uploaded files using token based replacement patterns to maintain a nice clean filesystem.



  • Configurable file paths now use node tokens instead of user tokens.
  • Configurable filenames.
  • Support for:
  • File path and filename cleanup options:
    • Filter out words and punctuation by taking advantage of the Pathauto module.
    • Convert unicode characters into US-ASCII with the Transliteration module.
  • Automatically updates unprocessed file paths in the node body, teaser and CCK text fields on save.
  • Retroactive updates - rename and/or move previously uploaded files (Use with caution)
  • [D6] Active updating - actively rename and/or move previously uploaded files (Use with caution)


Required Modules:


Recommended Modules:



Once installed, File (Field) Paths needs to be configured for each file type you wish to use.


Frequently Asked Questions:

  • Aren't tokens already supported in the FileField module?

    Only User tokens are supported in the FileField module.

    Node tokens allow you to use the Node ID, Node Title, Node creation date and much more in your directory/filenames where User tokens are very limited.
  • Why are my files uploaded to 'files/[nid]' instead of 'files/1'?

    When you are creating or updating a node the full values for the Node tokens may not yet be known by Drupal, so the File (Field) Paths module will upload your files to a temporary path based on your filepath pattern ('files/[nid]') and then once you save the node and Drupal is provided with the Node tokens values the file will be moved to the appropriate location.
  • Why is there a warning on the 'Retroactive updates' feature?

    Retroactive updates will go through every single node of the particular content type and move and/or rename the files.

    While there have been no reports of errors caused by the feature, it is quite possible that the moving/renaming of these files could break links. It is strongly advised that you only use this functionality on your developmental servers so that you can make sure not to introduce any linking issues.
  • What does File (Field) Paths offer that other similar modules do not?

    For an unbiased answer, please refer to the 'File Uploading and Managing' comparison chart at:


Release Dates: