In brief
- Project Setup lets users define project-specific settings and resources in Blender 5.3.
- The .blender_project folder in the project root helps Blender locate the project configuration.
- Projects can use their own asset libraries and OpenColorIO color configurations.
- A project-specific extension repository and multi-project workflow improvements are planned for Blender 5.4.
Blender developers Sebastian Parborg and Anastasia Rudina announced the features offered by Project Setup in Blender 5.3 on the official development blog on 13 November 2026. The optional system ties settings and resources to a single project, aiming to prevent preferences from getting mixed up when switching between different projects.
How are projects defined in Blender?
In Project Setup, a project is represented by a root directory that keeps related files together. The .blender_project folder in this directory contains the project.toml configuration file, which Blender creates and manages. When a .blend file is opened, Blender searches the file’s folder hierarchy for this project folder. If it finds one, it activates the project. If no project folder is found, the session is considered to be outside a project.
A project can also be opened by providing its directory path when launching Blender, or through File → Project → Open in the application. In the developers’ design approach, project settings take precedence over user preferences. Keeping settings files in a readable, editable format also makes it possible to generate them with external scripts or track them in version control.
What project features are in Blender 5.3?
The new system can use the {project_root} variable in output file paths. This means paths that rely on the variable follow the project root when the project is moved to another drive, computer or team member. Users can also define their own project variables, such as a character name, sequence code or frequently used folder, and use them in path templates. When a variable’s value is updated, paths that use it follow the new value.
Separate asset libraries can be defined for each project. While a project is open, these assets appear alongside other libraries in the Asset Browser, Asset Shelves and Add menus. Color management can also be set per project: users can choose Blender’s default configuration, ACES 1.3, ACES 2.0 or a custom OpenColorIO configuration. Projects can also have their own splash screen, which lists recent files from the same project.
What’s next for Blender 5.4?
The developers say Project Setup work will continue in Blender 5.4. The main goal is to let projects include their own extension repository folder and define extension settings on a per-project basis. This is intended to let people working on the same project use a shared toolset, while allowing the same extension to use different settings in different projects. These are development goals announced for the next release, not features available in 5.3.
Plans also include extending path templates and project variables to more paths in Blender. Multi-project improvements are also envisaged, including adding a project selector to the File Browser, limiting Save As to the active project, and leaving variables unresolved when using Save As Copy.
Impact on architecture and visualization workflows
Architecture firms and archviz teams can define separate asset libraries and color management settings for each project, keeping resources and visual settings for different jobs distinct. A portable project root and variable-based paths can also help keep file paths tied to the project structure for teams working with shared files. This approach is particularly useful for teams that work on multiple projects in rotation.
Before adopting the system, teams should review the Blender version they use, their project folder structure and how their existing paths are set up. Since the extension repository and multi-project features are planned for 5.4, teams making decisions based on these needs should not assume they are already available in the current release.
Sources
1 sourceSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
Project Setup’s strength is its potential to reduce the need for teams to manually recreate the same settings by keeping Blender preferences alongside project files. For offices in Turkey working on multiple client projects, separating asset libraries and color management by project could help establish a well-organized production workflow.
Still, adopting it involves more than simply creating a new folder: existing file paths, team habits and the versions in use should all be reviewed. The announcement provides no information about additional hardware, fees or licensing requirements. Since sharing extensions within a project and some multi-project conveniences are described as 5.4 goals, teams should keep track of the release scope rather than assume these features are ready to use.
Frequently asked questions
Which Blender version supports Project Setup?
Project Setup is available as an optional system in Blender 5.3.
Can color management be set per project in Blender?
Yes. A project can use Blender’s default color configuration, ACES 1.3, ACES 2.0 or a custom OpenColorIO configuration.
What features are coming to Project Setup in Blender 5.4?
The developers plan to work on a project-specific extension repository and settings, as well as multi-project workflow improvements. These are goals announced for 5.4, not existing 5.3 features.
