No. SceneSanity does not require an account, cloud service, telemetry, external Python packages or another Blender add-on for normal operation.

No. Many validation features are intentionally inspection-focused. SceneSanity can detect and report supported problems, but it does not silently reconstruct or repair arbitrary geometry, rigs, Geometry Nodes or UV layouts.

SceneSanity separates lightweight real-time processing from heavier inspections. Supported background work is incremental and bounded, while expensive geometry, UV and project inspections remain on demand. Extremely complex scenes or heavy Blender operations can still affect performance, so SceneSanity does not promise zero stalls in every project.

Yes. SceneSanity supports custom naming rules, prefixes, suffixes, collection matching and templates. Built-in workflows for High, Low, Cage, HP, LP and UCX are available, but they are not the only naming structure you can use.

SceneSanity can compare supported materials using shader structure, relevant properties and resource dependencies rather than relying only on names. This means equivalent supported materials may be detected even when they have different names, while materials with meaningful differences remain separate.

SceneSanity is designed conservatively. Supported replaced resources can be retained in Recovery instead of being immediately deleted. You can restore the latest supported retained cleanup batch and permanently empty Recovery only when you choose to. Ambiguous or unsupported cases may be skipped rather than guessed.