EVTX viewer: open Windows event logs in your browser
Drop a .evtx file (Security, System, Sysmon or any other channel) and every event appears in a table you can filter
by event ID or search, with the event IDs explained and the free analyzer's attack checks run on the same events. The file is read
in this browser tab and never uploaded.
What the viewer shows
Each event's time (UTC), event ID with Microsoft's title, result (audit success or failure), the account it is about, where it came from, and the fields that matter for that event: logon type, failure reason and codes, process and command line, Kerberos service and encryption, group changes, Sysmon images and targets. Click a row for every field with its meaning and decoded value. Click an event ID that has a page in the reference library, such as 4625 or 4688, for what it means and what to check next. The detections come from the same Windows checks as the log analyzer: password spraying, brute force, logins that succeed after failures, cleared logs and new admin accounts, among others. The same file opens in the log analyzer too, which shows the evidence rows behind each finding.
How the file is read
A .evtx file is not text: it is Microsoft's binary event log format, a 4 KB header followed by 64 KB chunks of records written in a compact binary XML. The viewer reads that format in JavaScript and turns each record into the same event XML that Event Viewer's "Save as XML" produces. The reader is tested record by record against python-evtx, a widely used open-source parser, on a sample System log of 1,601 events.
Exporting an event log
:: whole Security log (administrator prompt)
wevtutil epl Security C:\temp\security.evtx
:: only failed logons, the last 7 days
wevtutil epl Security C:\temp\failed-logons.evtx /q:"*[System[(EventID=4625) and TimeCreated[timediff(@SystemTime) <= 604800000]]]" Questions
- Is the .evtx file uploaded anywhere?
- No. The file is read by JavaScript in your browser tab; nothing is sent to LogTriage or anyone else. You can disconnect from the network after the page has loaded and it still works.
- Which event logs can it open?
- Any Windows event log file: Security, System, Application, Sysmon, PowerShell and the other channels, saved from Event Viewer as .evtx or copied from C:\Windows\System32\winevt\Logs. XML exports (Event Viewer "Save as XML", wevtutil qe /f:xml) open too. Files up to 100 MB.
- How do I copy the log off a Windows machine?
- In an administrator command prompt: wevtutil epl Security C:\temp\security.evtx. To keep only some events, add a query, for example /q:"*[System[(EventID=4625)]]". Event Viewer's "Save All Events As…" writes the same file.
- Can it read a damaged or partly overwritten log?
- Records that cannot be read are skipped and counted, so one damaged record does not lose the file. Records that Windows has overwritten in the file's free space are not recovered.
Need the whole story, not just the events?
LogTriage enriches every account, address and hash in a Windows log with threat intelligence and writes the incident report: timeline, impacted users, indicators and remediation steps.
Investigating something right now? LogTriage checks every address in the file against threat intelligence and writes the incident report: 10 analyses a month free. The incident pack adds the in-depth AI analysis and files up to 100 MB: 25 analyses for $19, one payment, no subscription. Pricing
Every query on this site's reference pages, the Sigma rules and a cheat sheet in one download: the Incident Response Kit, $29 once.