Find Oversized Log Files
Use this workflow on an authorized Windows 10 or Windows 11 computer. SpaceSniffer shows a size-proportional view of storage; always inspect the source file in Windows before changing or deleting it.
Step-by-step workflow
- Scan the relevant application directory.
- identify *.log or similar blocks.
- determine which app writes them.
- rotate or clear using that app's supported controls..
How to verify the result
The growing log source is identified and subsequent file growth can be monitored.
Why this matters
SpaceSniffer is a visualization tool, not a diagnosis of file necessity. The important outcome is an identifiable path and measurable file size, checked against the same Windows volume and with permission to inspect it. If the scan is incomplete, report that limitation instead of treating missing paths as zero bytes.
More targeted troubleshooting
If the result differs from what File Explorer reports, clear the filter field, allow scanning to finish and check the permissions of the specific directory. Repeat on a smaller known folder when you need to isolate a scanning limitation. Always distinguish a changed treemap view from an actual change in free space.
Frequently asked questions
What is the first step for find oversized log files?
Scan the relevant application directory.
How do I check the result?
The growing log source is identified and subsequent file growth can be monitored.
What should I avoid?
Do not erase logs needed for troubleshooting or compliance.
Related Windows topics
- What Changed in SpaceSniffer 2.2.0.27?
- Verify a SpaceSniffer ZIP Download
- Use SpaceSniffer Without Installing
- SpaceSniffer on Windows 11
Sources and further reading
Get the portable Windows application
Confirm the version, compatible architecture, package hash and provenance before executing a downloaded archive.
SpaceSniffer