I built a tool for reviewing large collections of GLB/glTF files without opening each one individually.

Core idea: load a folder, navigate with arrow keys, tag issues, filter by validation errors.

Technical highlights: - Three.js for rendering - glTF-validator integration - IndexedDB caching with content hashing - Web Workers for parallel indexing - 100% client-side (File System Access API)

Features: QA tagging, validation reports, animation playback, texture inspection, JSON export.

Useful for game devs doing asset QA or anyone managing 3D model libraries.

https://glb.arysociety.com/

For a game asset pipeline, being able to export that 'reject list' to JSON is huge. Does the JSON output include the absolute file paths? I'm thinking about how easily I could script a cleanup script to auto-delete the rejected assets based on your tool's export.