Blender 5 ACES HDR Color Pipeline for Indie Game Assets - 2026 Checklist

Blender 5 changed color management in a way that matters for game teams, not only film finishing houses. Blend files now carry an explicit working color space. You can choose Linear Rec.709 (the familiar default), Linear Rec.2020, or ACEScg. Display options include ACES 1.3 and 2.0 views, AgX HDR, and Rec.2100 PQ/HLG for HDR video targets (Blender 5.0 color management release notes; Displays and Views manual).

That is production truth in 2026. It is also a trap for indies who treat “ACES” as a magic checkbox, then export a glTF into Unity, Godot, or Unreal and wonder why the hero prop looks washed, pink, or neon compared to the Blender viewport.

This checklist is the game-asset answer to that gap. Official docs explain ACES views and ACEScg for wide-gamut pipelines. Film coverage dominates the SERP. Indies need a different spine: pick a working space once, lock display and view for the job, tag textures correctly, export for engines that still expect sRGB albedo + Non-Color data maps, then smoke the import on three engines before a partner ever opens the zip.

Direct answer: For most indie game props in July 2026, keep Linear Rec.709 as the working space unless you have a contractual ACES pipeline. Use ACES or HDR views only when you are matching film deliverables or HDR trailer masters. Never confuse a view transform with the texture color spaces your engine will read. Clear gates B1–B8, file blender_aces_game_asset_receipt_v1.json, and latch blender_aces_ok.

If your problem is already a washed Unity albedo, jump to the Blender color space looks wrong in Unity help fix. If you need scale, pivots, and material packing first, use the Blender to Unity and Godot export handoff checklist. This URL owns working-space and HDR/ACES decisions for game props, not hero GLB hash mirrors (that evening lives here).

Why this matters now (July 2026)

Blender 5.0 shipped with working-space support and ACES/HDR display options as first-class features (release notes; color management notes). That is durable production truth, not a seasonal gimmick. Search and studio discourse still treat “blender aces” as a film-finishing phrase. Game teams that adopt ACEScg without an engine plan re-bake albedo, fight partner review screenshots, and invent one-off OCIO configs the week before a store capture pass.

What changed for micro-studios:

1. Working space is a file-level decision. Changing it mid-project approximates colors and often needs manual fix-ups (release notes).
2. ACES views are available without a custom OCIO fight. Tempting for trailer look-dev. Dangerous if you bake look into albedo for an sRGB engine.
3. HDR display and export exist. Useful for trailer masters and HDR monitors. Not the same as “ship HDR textures into a Steam Deck build.”
4. Engine truth did not flip overnight. Most Unity URP/HDRP, Godot, and Unreal game materials still assume sRGB base color and linear data maps. Your Blender 5 upgrade does not rewrite that contract.

Time budget: 2–4 hours for a first locked template file, one proof prop, and three-engine smoke. Prerequisites: Blender 5.0+, one glTF-capable target engine, a neutral grey reference material, and a folder release-evidence/blender-aces-checklist/.

Non-repetition (what this URL owns)

Forward cluster rows: Help for Blender 5 ACEScg→engine pink albedo (forward); Resource Blender ACES + export tools (forward); Guide chapter on Blender 5 color (forward).

Beginner glossary (five terms, no film school)

Working space — The scene-linear color space Blender uses for materials, lights, and compositing inside the .blend. Blender 5 defaults to Linear Rec.709; ACEScg and Linear Rec.2020 are options. Pick early; convert later only with eyes open.

Display — The target device space for what you see (sRGB, Display P3, Rec.2100-PQ, Rec.2100-HLG). Choose based on output target, not fashion (Displays and Views).

View (view transform) — The tone-mapping path from scene-linear to the display (AgX, Filmic, ACES 1.3, ACES 2.0, AgX HDR, Raw). A view changes how you preview. It is not automatically how a game engine samples a PNG albedo.

sRGB texture — Color images (albedo/base color) that engines usually interpret as sRGB. Wrong flag = washed or muddy look.

Non-Color / Linear data — Normal, roughness, metallic, AO, masks. Must not get an sRGB curve. Wrong flag = shiny chaos.

ACES (for this checklist) — A family of industry color transforms. In Blender 5 you mainly meet ACEScg working space and ACES 1.3 / 2.0 views. “We use ACES” without saying which of those two you mean is how teams talk past each other.

Checklist at a glance (print this)

• [ ] B1 Blender 5.0+ confirmed; Color Management panel documented in the project README
• [ ] B2 Working space chosen and frozen for the project (usually Linear Rec.709 for indie game props)
• [ ] B3 Display + View locked to the job (viewport look-dev vs HDR trailer vs partner stills)
• [ ] B4 Texture nodes tagged — albedo sRGB, data maps Non-Color
• [ ] B5 Neutral grey + Macbeth-style swatch plane exists in the template file
• [ ] B6 Export path defined (glTF/GLB or engine-specific) with no accidental view baked into albedo
• [ ] B7 Unity + Godot + Unreal (or your two engines) import smoke signed
• [ ] B8 Receipt JSON filed; blender_aces_ok latched

Step 0 - Confirm Blender 5 and open Color Management (B1)

Help → About Blender. You need 5.0 or newer for file working space and the ACES/HDR display set described here. Older 4.x files open, but you should not invent a fake ACES pipeline with a half-migrated config unless you already own that OCIO stack.

Open Render Properties → Color Management (or the equivalent Color Management section in the Scene). Write these four fields into docs/color-pipeline.md for the repo:

Success check (B1): A teammate can open a fresh clone, read docs/color-pipeline.md, and match your Color Management panel without Slack archaeology.

Pro tip: Blender 5 shows descriptions for displays, views, and color spaces in the UI. Hover them. Do not memorize marketing slides.

Step 1 - Pick working space once (B2) - ACEScg vs Linear Rec.709

Blender’s own notes are blunt: the working space affects all data-blocks, has a significant effect on rendering and compositing, and should be chosen at the start of a project for all blend files. Conversion between spaces is approximate and often needs manual fix-ups (release notes).

Decision table for game studios

Beginner path (recommended default)

1. Leave Working Space = Linear Rec.709.
2. Do not toggle ACEScg “to see if it looks cooler.”
3. Use ACES views later only if a trailer brief requires them — on a copy of the shot file if needed.

Working-dev path (when ACEScg is honest)

Use ACEScg when:

• A partner zip explicitly requires ACEScg EXRs or an ACES OCIO config.
• Cinematics and game meshes share materials under one supervised pipeline.
• You have a documented engine transform (LUT / OCIO / custom shader path) — not a hope.

If you change Working Space on an existing file, use Blender’s convert option, then re-check albedo, emission, and light values on a proof sphere. Linked and appended assets convert automatically, but automatic is not perfect.

Success check (B2): Project README states one working space. Spot-check three random props; Color Management working space matches.

Step 2 - Lock display and view to the job (B3)

Display and view answer “what am I looking at,” not “what does the PNG contain.”

Job → lock map

Blender documents HDR display requirements: capable monitor; Apple Silicon on macOS; Wayland + Vulkan on Linux; Windows HDR/auto color management + Vulkan backend (release notes). OS/browser/player inconsistencies are real. Treat HDR preview as approximate until you verify on the target player.

HDR video export note (trailer lane, not mesh lane)

For HDR video writing, Blender’s pipeline notes say: set display to Rec.2100 PQ or HLG, prefer H.265 or AV1, use 10 or 12-bit depth. Bit depth 10 with PQ is a practical compatibility default (pipeline I/O notes; Displays and Views).

Do not bake that HDR trailer look into the albedo PNG you ship to Godot.

Success check (B3): Each template file’s Color Management matches the job table above. Trailer templates are separate from prop templates.

Step 3 - Texture tags before any ACES debate (B4)

Most “Blender ACES ruined my game” tickets are actually wrong texture color spaces.

Required tags

Quick verification ritual

1. Place a 0.18 grey albedo sphere next to your prop.
2. Import into the engine under a neutral HDRI or grey light.
3. If grey matches but the prop does not, your art is the issue. If grey washes too, import flags or project color space are wrong — see the Unity sRGB/Linear help page.

Success check (B4): A scripted or manual audit of Image Texture nodes finds zero data maps set to sRGB.

Step 4 - Build a color proof plane into the template (B5)

Create a small plane (or card) in every game-prop template with:

• Mid grey (0.18 scene-referred intent)
• White and near-black patches
• One saturated primary (team brand red or cyan)
• Optional Macbeth-style strip if your lead wants it

Render or viewport-capture this card under the locked Display/View for the job. Save proof-card-blender.png into release-evidence/blender-aces-checklist/. After engine import, capture proof-card-engine.png under neutral lighting.

Success check (B5): Side-by-side proof cards exist for Blender and at least one engine. Differences are explained in the receipt notes (expected view transform vs bug).

Step 5 - Export without baking the view into albedo (B6)

glTF / GLB (default indie path)

glTF consumers expect conventional PBR: sRGB base color textures, linear metallic-roughness. Your Blender working space and view transform should not silently rewrite albedo into an ACES display encoding.

Practical rules:

1. Export from a prop template locked to Linear Rec.709 + sRGB display for everyday game assets.
2. Do not enable experimental “save as display” paths for albedo unless you know you are writing a look-dev still, not a texture.
3. Keep materials Principled-compatible; exotic node graphs often round-trip poorly.
4. Apply transforms; freeze scale; follow the clean handoff checklist for non-color issues.

OpenEXR / stills for partners

When a partner asks for linear EXR:

• Document working space in the filename or sidecar (hero_acescg.exr vs hero_lin709.exr).
• Prefer explicit Color Interop metadata when available (Blender 5 improved EXR color metadata).
• Never hand them a PNG that already has ACES 2.0 view baked in and call it “linear.”

Trailer stills vs textures

Success check (B6): Albedo histogram in an image tool looks like a texture, not a graded poster. File name and README agree on encoding.

Step 6 - Engine import smoke (B7)

Run the same proof prop through every engine you ship to. Record pass/fail in the receipt.

Unity (URP or HDRP)

• Project Color Space = Linear (modern default).
• Albedo: sRGB On.
• Normal/Mask/ORM: sRGB Off.
• Neutral light + grey sphere comparison.
• If mismatch persists, follow Unity color mismatch help.

Godot 4.x

• Base color as color; roughness/metallic/normal as non-color imports.
• Check StandardMaterial3D / ORMMaterial3D channel packing if you use packed maps (ORM flat metallic help when relevant).
• Compare under a neutral Environment; disable aggressive tonemap experiments during the first smoke.

Unreal Engine

• sRGB on color textures; off on data.
• Confirm Sampler Type matches.
• View under a neutral HDRI; avoid “fixing” color with Post Process Volume during the smoke.

Optional Steam Deck / mid-PC note

If Godot 4.7 HDR output or Unreal MegaLights are in play for runtime HDR, that is an engine lock problem — see Godot 4.7 upgrade lock and Unreal 5.8 ship-date lock. Do not solve runtime HDR by secretly ACEScg-baking albedo.

Success check (B7): Written PASS on each target engine for grey sphere + hero prop under neutral light. Screenshots filed.

Step 7 - File the receipt and latch (B8)

Create release-evidence/blender-aces-checklist/blender_aces_game_asset_receipt_v1.json:

{
  "schema": "blender_aces_game_asset_receipt_v1",
  "blender_version": "5.0.x",
  "working_space": "Linear Rec.709",
  "display_device": "sRGB",
  "view_transform": "AgX",
  "acescg_used": false,
  "proof_prop": "props/proof_crate.glb",
  "engines_smoked": ["Unity 6 URP", "Godot 4.7", "Unreal 5.8"],
  "gates": {
    "B1": "pass",
    "B2": "pass",
    "B3": "pass",
    "B4": "pass",
    "B5": "pass",
    "B6": "pass",
    "B7": "pass",
    "B8": "pass"
  },
  "notes": "No ACEScg for game props; trailer HDR lives in separate shot files.",
  "blender_aces_ok": true,
  "checked_at": "2026-07-19"
}

Latch blender_aces_ok only when B1–B8 are pass. Partner diligence language can then say: “Color pipeline locked; working space and engine smoke attached.”

Success check (B8): CI or release checklist refuses “art final” without blender_aces_ok: true.

What changed in Blender 5 (trend section for teams still on 4.x)

If your art lead is still on Blender 4.2 LTS for a ship branch, the durable question is not “is ACES cool.” It is “when do we migrate files.”

Blender 5 adds:

• File working space (Linear Rec.709 / Linear Rec.2020 / ACEScg)
• ACES 1.3 and 2.0 views (SDR and HDR variants)
• AgX HDR view
• Rec.2100-PQ and HLG displays
• HDR/wide-gamut image and video write paths
• Color picker Linear vs Perceptual RGB editing
• Scene-linear brush/palette colors with sRGB editing
• BLENDER_OCIO env var scoped to Blender
• Warnings when a file was authored under a different OCIO config

For a live ship in two weeks, freeze the DCC version like any other dependency. For a new project starting this month, author on Blender 5 with the Rec.709 game-prop default above unless contract says otherwise. Pair engine HDR bets with the Godot/Unreal lock posts already linked — DCC HDR preview is not a substitute for those decisions.

Company / partner diligence language

Use this block in a partner README:

Game mesh and texture color pipeline: Blender 5 working space Linear Rec.709. Viewport display sRGB with team view AgX (or Filmic). Albedo textures tagged sRGB; data maps Non-Color. glTF exports are authored for conventional engine PBR. ACES views / ACEScg / Rec.2100 HDR are reserved for cinematic and trailer masters in separate files. Engine smoke screenshots and blender_aces_game_asset_receipt_v1.json are included in release-evidence/blender-aces-checklist/.

That paragraph prevents a producer from assuming ACEScg EXRs will appear in the game zip because someone saw “ACES” in a Blender 5 changelog.

Cost/ROI note for leads: one locked template file plus a two-hour smoke costs less than a week of “why is the capsule pink” Slack threads before a sale.

Common mistakes

1. Turning on ACEScg mid-project because YouTube said so. Working space is a project contract.
2. Using ACES 2.0 view, then saving albedo “as rendered.” You baked a look into a texture.
3. Assuming HDR display = HDR game textures. Trailer lane ≠ mesh lane.
4. Leaving roughness on sRGB. Instant broken metal.
5. Comparing Blender AgX preview to engine ACES tonemapper. Different transforms; use the grey sphere.
6. One OCIO config on the artist laptop, another on CI. Use BLENDER_OCIO intentionally and document it.
7. Converting working space without re-checking emission and lights. Approximate conversion hides in highlights.
8. Skipping Godot or Unreal because “Unity looked fine.” Importers disagree.
9. Mixing Blender 4 and Blender 5 files without reading OCIO warnings. New warnings exist for a reason.
10. Fixing store-capsule bloom by regrading albedo. Capsule HDR problems belong in the winter HDR capsule pass, not in prop textures.

Two-evening schedule

If you only have one evening, finish B2 + B4 + one-engine smoke. Do not “half enable ACEScg.”

Related resources and next steps

• Guide: Blender asset pipeline chapter
• Help: Blender color wrong in Unity
• Resource: 25 free Blender-to-engine workflow resources
• Blog: AI 3D import-ready checklist when assets start from generators instead of hand-authored maps

Key takeaways

• Blender 5 adds real working-space choices (Linear Rec.709, Linear Rec.2020, ACEScg) plus ACES and HDR views.
• Most indie game props should stay on Linear Rec.709 unless a contract forces ACEScg.
• Display and view locks serve the job (props vs HDR trailer); they are not free albedo upgrades.
• Wrong texture tags cause more “ACES bugs” than ACES itself.
• Never bake an ACES/HDR view into game albedo.
• Proof cards and grey spheres beat opinion in Slack.
• Smoke Unity, Godot, and Unreal (or your actual targets) before partner review.
• Keep cinematic ACEScg/HDR files separate from game-prop templates.
• Document the pipeline in README language a producer can paste.
• Latch blender_aces_ok only after gates B1–B8 pass.
• Pair DCC locks with engine HDR adopt/hold posts — they solve different layers.
• Durable skill: color contracts beat changelog tourism.

FAQ

What is Blender ACES in Blender 5?

In Blender 5, “ACES” usually means either the ACEScg working space for scene-linear authoring or the ACES 1.3 / 2.0 view transforms for display. They are related but not interchangeable. Game teams must say which one they mean.

Should indie games use ACEScg for props?

Usually no. Linear Rec.709 remains the safer default for assets destined for Unity, Godot, or Unreal PBR. Use ACEScg when a partner pipeline or shared cinematic stack requires it and you have a documented engine transform plan.

Does enabling an ACES view change my exported textures?

A view transform changes preview (and outputs you explicitly save with the view applied). It does not magically fix engine import flags. Saving “as rendered” albedo is how looks get baked into textures by mistake.

How do I export HDR video from Blender 5?

Set display to Rec.2100-PQ or HLG, use H.265 or AV1, and prefer 10- or 12-bit depth per Blender’s pipeline notes. Keep that workflow in trailer files, not in game-prop albedo exports.

Why does my prop look washed in Unity after Blender 5?

Most often: albedo not marked sRGB, project still in Gamma, or you compared AgX preview to a different engine tonemapper. Follow the Unity color mismatch help and re-run the grey-sphere smoke.

Can I convert an old Blender 4 project to ACEScg?

Blender can convert working spaces, but conversion is approximate and often needs manual fix-ups. Convert a hero file first, compare materials and lights, then decide. Do not batch-convert a ship branch days before Gold.

Is Blender 5 HDR display required for Steam store captures?

No. Store captures have their own downscale and bloom traps. Use the winter HDR capsule art pass for that lane. Author props with a stable Rec.709 + sRGB texture contract first.

What should I put in a partner diligence zip?

Working-space statement, display/view locks for game vs trailer files, proof-card screenshots, engine smoke notes, and blender_aces_game_asset_receipt_v1.json with blender_aces_ok.

Conclusion

Blender 5 finally makes blender aces a first-class DCC conversation — and that is exactly why game teams need a boring checklist. ACEScg and HDR views are real tools. They are also easy to misuse as fashion. Lock working space early, tag textures like an adult, keep trailer HDR in trailer files, smoke the engines, and file the receipt.

Bookmark this page for the next art-pipeline onboarding. Share the diligence paragraph with producers. When someone pastes a pink screenshot into Discord, you will already know whether you are looking at a working-space mistake, a texture flag, or an engine tonemapper argument — and you will have the grey sphere to prove it.