Validating glTF
Solidly can validate a glTF or GLB file against the official Khronos glTF validator and report the result in the inspector.
Direct download only
Validation is not available in the Mac App Store build, where the Health section does not appear. See The two distributions.
Running validation
Validation starts automatically when a glTF or GLB model loads. The result appears in the Info tab's Health section, under a Validator disclosure whose header carries a status badge:
| Badge | Meaning |
|---|---|
| Running | Validation is in progress |
| A summary of the issues found | Validation finished |
| Unavailable | The validator could not be run, with the reason shown inside the disclosure |
The button beside the badge runs validation again, which is useful after making edits or after saving.
Reading the report
The validator classifies each finding by severity, and the report lists them with the message and the location in the document it applies to. The severities are the validator's own:
- Errors are violations of the specification. A file with errors is not a valid glTF, and other tools may refuse it or render it incorrectly.
- Warnings describe things that are legal but likely to be wrong, such as an accessor whose declared bounds do not match its data.
- Information and hints cover observations that are not defects, such as an unused resource.
An asset that loads and renders correctly in Solidly can still report errors, because Solidly's loaders tolerate more than the specification requires. The validator is the authority on whether the file is correct; the viewport is the authority on what it looks like.