I built nEVEn (read like uneven) to help diagnose and reduce SketchUp slowdowns, crashes, and viewport lag in large production models.

A Real World Example.

An almost empty SketchUp model was still 566 MB, despite containing almost no geometry or materials.

The Session Log

The geometry and texture inventories were empty, but the Session Log showed a large amount of Embedded Data stored inside the model.

The Scan uncovered issues that were caused by hidden data stored inside the SketchUp model.

RESCAN

Ran with nEVEn Purge + Save workflow.

The model was reduced from 566 MB to 0.1 MB and returned to a clean state.

This model came from a recent SketchUp Community discussion.

https://forums.sketchup.com/t/topic/348351/10?u=n1lesh

A question for the community.
Cases like this show that not every SketchUp problem is caused by geometry or textures.

Where should nEVEn go next?

Should development continue focusing on optimization and model cleanup, or move further into helping explain the parts of SketchUp that aren’t normally visible?

What problems should nEVEn solve next?

Real-world examples are always welcome.

nEVEn v5.34 is now available with SketchUp Native White theme.

Download : n1leshtools.com

No signup. No account required. Just install and use.