Blender 5.3 introduces Project Setup with per-project settings, asset libraries, and variables

Blender 5.3 ships Project Setup, an opt-in system that replaces the previous global-preference model with per-project configuration. A project is defined by a .blender_project folder containing a project.toml file; Blender detects this by walking up the directory tree from any opened .blend file. Project settings override user preferences, and the plain-text format enables version control integration and external scripting.

The initial release brings four concrete features: path templates with built-in and custom variables, per-project asset libraries surfaced in the Asset Browser and Add menus, per-project OpenColorIO configuration including ACES 1.3 and 2.0, and custom splash screens with project-scoped recent files. Blender 5.4 will extend this with per-project extension repositories, broader path variable coverage, and multi-project workflow improvements including a File Browser project selector.

What Project Setup changes in Blender 5.3

• Project detection and configuration: Blender locates projects by searching upward for a .blender_project folder containing project.toml, and can also open a project directly via blender /path/to/project or File > Project > Open.
• Path templates and variables: Output paths support {project_root} and {project_name} built-ins, plus user-defined custom variables, enabling portable path references across machines without relying solely on .blend-relative paths.
• Per-project asset libraries: Project-specific asset libraries appear in the Asset Browser, Asset Shelves, and Add menus alongside global libraries, keeping production assets scoped to their project.
• Per-project color management: Each project carries its own OpenColorIO configuration selection (Blender default, ACES 1.3, ACES 2.0, or custom), ensuring consistent color pipelines for all contributors without manual preference switching.
• Plain-text, version-control-friendly format: The project.toml file is designed for external editing, diffing, and tracking in version control, aligning with studio pipeline automation practices.

Why it matters

For Linux-based animation and VFX studios, Project Setup reduces the friction of multi-project workflows where artists previously had to manually swap global preferences or maintain fragile relative paths across network mounts. The plain-text project.toml format integrates cleanly with existing Git-based asset pipelines and automated deployment tools common in open-source production environments. Blender 5.4's planned per-project extension repositories will further reduce onboarding time by ensuring add-on versions and settings travel with the project rather than requiring manual workstation configuration.