OCIO Validator is a free, local-first checker for OpenColorIO configs. Paste a config.ocio and it confirms every role, view, display, look and view transform resolves to a defined colorspace, flags broken references and duplicates, and gives an ACES-config advisory. It validates structure, not the colour math - and everything runs on your machine.
Because config.ocio is plain-text YAML, a whole OpenColorIO config can be resolved right in the browser - so you can confirm it hangs together before an app ever loads it.
Every role, view, display, look and view transform is checked against the colorspaces you actually defined - including aliases and named transforms.
Structural issues that trip up a config: duplicate or unnamed colorspaces, empty displays, missing standard roles, and active displays/views that point to nothing.
Detects an ACES config and advises when the reference or scene_linear roles differ from the usual ACES2065-1 / ACEScg - then lets you browse every role, colorspace, display and view.
When Nuke, Maya, Houdini or a render farm throws "could not find color space", the cause is almost always a role, view or look pointing at a name that isn't defined - often a typo or an alias that changed. OCIO Validator lists every one of those in seconds.
Open a studio or vendor config and immediately see its roles, colorspaces, displays and views - and whether they all hang together - without standing up an OpenColorIO build just to run ociocheck.
Confirm an ACES config has its reference role on ACES2065-1 and scene_linear on ACEScg, that Raw is flagged as data, and that your displays and views resolve - the small things that quietly cause wrong-looking renders.
OCIO Validator is a PWA: install it and it keeps working with no network. Because it never needed a server, offline is simply the default.
Load or paste the config text. It's YAML, so the whole thing parses in the browser - no OCIO install needed.
A clean / warnings / invalid verdict, metrics, and findings grouped error → warning → info, each with a code.
Explore roles, colorspaces, displays and views, then export the findings as JSON or CSV. Nothing ever left your browser.
There is no server to send your work to. All parsing and validation run as plain JavaScript in your browser. Your config, colorspace names and view names stay on your device - which is exactly what you want when the show is under NDA.
OCIO Validator reads config.ocio as YAML text and checks that the config is internally consistent: references resolve, names are unique, and the roles/views/displays/looks/view-transforms all point at things that exist. It supports OCIO v1 and v2 shapes (including view_transform + display_colorspace views).
It does not run the OpenColorIO library, resolve LUT files on disk, or verify that any transform is colour-scientifically correct. Treat it as a fast pre-flight, then confirm anything important with ociocheck or in your DCC. General information, not colour-science advice.
OCIO Validator checks one config.ocio. Nuke Studio Hub audits your Nuke .nk scripts: Write-node output paths and naming, broken or absolute Read media, node-naming hygiene and a colour / OCIO audit across the whole comp - plus CSV/PDF reports. Step up when one config isn't the whole picture.
config.ocio is the OpenColorIO configuration file - a YAML text file that defines the colorspaces a facility works in, the roles that map generic names like scene_linear or data to those colorspaces, and the displays and views used for viewing (plus looks and, in OCIO v2, view transforms). More on how a config is structured →view_transform plus a display_colorspace), that looks and their process spaces exist, and that active_displays / active_views refer to things that are defined. It flags duplicate or unnamed colorspaces and missing standard roles, and gives ACES advisories. It does not run the OpenColorIO library and does not verify the colour math.config.ocio text you paste or load never leaves your device.ociocheck loads a config with the real OpenColorIO library. OCIO Validator reads the config as text in the browser, so it is a fast structural pre-check you can run anywhere without an OCIO install - but you should still verify anything important with ociocheck or in your DCC before relying on it. Read: ACES OCIO configs explained →ocio_profile_version 1 and 2 configs, including v2's display_colorspaces, view_transforms, named_transforms and views written as view_transform + display_colorspace. Binary is not involved - a config is always YAML text.