.log · text/plain
What is a .log file?
Log File
About the format
A .log file is a program's diary: timestamped lines recording what it did and what went wrong, in whatever format its authors chose. Windows and its components scatter them everywhere — CBS.log for system-file servicing (where sfc /scannow writes its findings), setupact.log for setup, dism.log, driver installation logs, plus every third-party app's own. Reading strategy beats format knowledge: go to the END of the file (logs are chronological, and you usually care about the latest failure), search for ERROR, FAIL or WARN, then read the lines just before the first error — causes precede symptoms. Big logs choke Notepad; use a viewer that handles large files or PowerShell's Get-Content -Tail. Logs are also the polite currency of support: attaching the right .log to a bug report is often the difference between a guess and a fix. They're safe to open, safe to delete when huge and stale (the program recreates them), and worth skimming before assuming a crash left no trace.
How to open a .log file
Windows
- Notepad / Notepad++ (large files)
- PowerShell Get-Content -Tail 100
macOS
- Console, any editor, tail
Linux
- less, tail, any editor
Is a .log file dangerous?
No. Privacy is the only consideration — logs can contain paths, usernames and addresses.
Related file types
Not sure what a file is? Check its bytes.
File names lie; magic numbers don't. Drop any file into the identifier — nothing is uploaded.
Identify a file →