Blender’s Directory Layout¶
This page documents the different directories used by Blender.
This can be helpful for troubleshooting, automation and customization.
User Directories¶
User directories store preferences, startup file, installed extensions, presets and more. By default these use the standard configuration folders for each operating system.
Linux¶
$HOME/.config/blender/4.3/
If the $XDG_CONFIG_HOME environment variable is set:
$XDG_CONFIG_HOME/blender/4.3/
macOS¶
/Users/$USER/Library/Application Support/Blender/4.3/
Windows¶
%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\4.3\
Portable Installation¶
When running Blender from a portable drive, it’s possible to keep the configuration files on the same drive to take with you.
To enable this, create a folder named portable at the following locations:
Windows: Next to the Blender executable, in the unzipped folder
Linux: Next to the Blender executable, in the unzipped folder
macOS: Inside the application bundle at
Blender.app/Contents/Resources
This folder will then store preferences, startup file, installed extensions and presets.
Environment Variables¶
The BLENDER_USER_RESOURCES environment variable
can be set to a custom directory to replace the default user directory.
System Directories¶
System directories store files that come bundled with Blender and are required for it to function. This includes scripts, presets, essential assets and more.
Linux¶
Archive downloaded from blender.org:
./4.3/
Linux distribution packages:
/usr/share/blender/4.3/
macOS¶
./Blender.app/Contents/Resources/4.3/
Windows¶
Zip file downloaded from blender.org:
./4.3/
Installer downloaded from blender.org:
%ProgramFiles%\Blender Foundation\Blender\4.3\
Microsoft Store installation:
%ProgramFiles%\WindowsApps\BlenderFoundation.Blender<HASH>\Blender\4.3\
Environment Variables¶
BLENDER_SYSTEM_SCRIPTS and BLENDER_SYSTEM_EXTENSIONS
environment variables
can be used to bundle additional scripts and extensions,
that are not part of the regular Blender installation.
Other BLENDER_SYSTEM environment variables can override other system paths,
though are not commonly used in practice.
Path Layout¶
./autosaveAutosave blend-file location. (Windows only, temp directory used for other systems.)
Located in user directories.
./configUser configuration and session info.
Located in user directories.
./config/startup.blendBlend file to load on startup.
./config/userpref.blendUser preferences.
./config/bookmarks.txtFile Browser bookmarks.
./config/recent-files.txtRecent file menu list.
./config/{APP_TEMPLATE_ID}/startup.blendStartup file for an application template.
./config/{APP_TEMPLATE_ID}/userpref.blendUser preferences file for an application template.
./datafilesData files loaded at runtime.
Located in both user and system directories. User data files either override or add to system data files.
./datafiles/colormanagementDefault OpenColorIO configuration.
./datafiles/fontsUser interface fonts.
./datafiles/studiolightsStudio light images for 3D viewport.
./extensionsExtension repositories.
Located in both user and system directories. Repositories are loaded from both directories.
./scriptsAdd-ons, presets, templates, user interface, startup scripts.
Located in both user and system directories. Scripts are loaded from both directories.
./scripts/addons/*.pyPython add-ons which may be enabled in the Preferences include import/export format support, render engine integration and many handy utilities.
./scripts/addons/modules/*.pyModules for add-ons to use (added to Python’s
sys.path)../scripts/addons_core/*.pyThe add-ons directory which is used for bundled add-ons.
./scripts/addons_core/modules/*.pyModules for
addons_coreto use (added to Python’ssys.pathwhen it found)../scripts/modules/*.pyPython modules containing our core API and utility functions for other scripts to import (added to Python’s
sys.path)../scripts/startup/*.pyScripts which are automatically imported on startup.
./scripts/startup/bl_app_templates_user/{APP_TEMPLATE_ID}Application templates installed in user directories.
./scripts/startup/bl_app_templates_system/{APP_TEMPLATE_ID}pplication templates automatically loaded from system directories.
./scripts/presets/{preset}/*.pyPresets used for storing user-defined settings for cloth, render formats, etc.
./scripts/templates_py/*.pyExample scripts which can be accessed from .
./scripts/templates_osl/*.oslExample OSL shaders which can be accessed from .
./pythonBundled Python distribution.
Located in system directories.
Local Cache Directory¶
The cache directory is used to store persistent caches locally. Currently it is only used for the indexing of Asset Libraries. The operating system is not expected to clear this automatically.
The following path will be used:
- Linux:
$XDG_CACHE_HOME/blender/if$XDG_CACHE_HOMEis set, otherwise$HOME/.cache/blender/
- macOS:
/Library/Caches/Blender/
- Windows:
%USERPROFILE%\AppData\Local\Blender Foundation\Blender\Cache\
Temporary Directory¶
The temporary directory is used to store various files at run-time (including render layers, physics cache, copy-paste buffer and crash logs).
The temporary directory is selected based on the following priority:
User Preference (see File Paths).
Environment variables (
TEMPon Windows,TMP&TMP_DIRon other platforms).The
/tmp/directory.