Dmesg Timestamp Converter
Convert Linux dmesg log timestamps (seconds since boot) into real dates and times, using a reference point you provide to calculate boot time.
Dmesg timestamps count seconds since your system booted, not since a fixed calendar date - your browser has no way to know when that was. Provide one reference point (a timestamp from dmesg and the real date/time it corresponds to) so this tool can calculate your system's boot time and convert other entries from there.
Step 1: Calibrate
Defaults to right now - accurate if you just ran dmesg and used its last line above.
Step 2: Convert another timestamp
Recommended Settings
Pro Tips
- •The easiest calibration point is the last line of a dmesg output you just ran - use that timestamp with 'now' as the real time
- •Once calibrated, you can convert as many other dmesg timestamps from that same boot session as you like
- •This calculation assumes your system clock wasn't adjusted (e.g. by NTP drift correction) between boot and now - for most desktop and server use, this is accurate enough
- •If your system reboots, you'll need to recalibrate, since the boot time reference changes
Most Popular
Most users calibrate using dmesg's last line and the current time, since that's what's on screen right after running the command
When to Use This Tool
Figure out exactly when a kernel log event happened in real-world time.
Map dmesg boot-relative timestamps to actual dates while diagnosing an issue.
Build an accurate timeline of system events during an incident investigation.
Determine when a hardware error or device event actually occurred.
How It Works
Use your provided reference pair to calculate the system's boot time: real time minus the dmesg seconds-since-boot value
Apply that same boot time offset to any other dmesg timestamp you enter
Display the resulting real date and time in both your local timezone and UTC
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Client-side offset calculation from a user-provided reference point for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
Why can't this convert a dmesg timestamp automatically, without a reference?
Dmesg timestamps only count seconds since your system booted - they carry no information about which real-world date and time that boot happened. A browser tool has no way to know your computer's actual boot time without you providing a reference point.
How accurate is this?
It's accurate as long as your system clock hasn't been significantly adjusted since boot (for example, by NTP correcting a clock that was initially wrong) - for typical modern systems, this is usually accurate to within a second or so.
Can I convert multiple dmesg timestamps at once?
Calibrate once, then convert as many timestamps as you like from that same boot session - each conversion just reuses the calculated boot time offset.
Is my data sent to a server?
No. All calculation happens entirely in your browser.
What if my system has been suspended/hibernated?
Suspend and hibernate can affect how the kernel's boot-relative clock behaves depending on your system, which may introduce inaccuracy - a calibration point taken close in time to the entry you're converting will generally be most reliable.