Paste a dump or load a local file to review the captured threads. The analyzer correlates information in that snapshot; it does not monitor a running JVM.
Runs locally in your browserJVM Thread Dump Analyzer belongs to the archive tools on KivTools. The workbench above handles the whole job on one screen: files chosen from your device, then a file you download.
The conversion runs inside the page with browser JavaScript. Nothing you enter is uploaded, the tool keeps working offline, and it is safe for data you are not allowed to send to a third party.
Binary formats carry more than the content you see: metadata, colour profiles, embedded fonts and, in practice, a fair amount of information you did not intend to publish. These tools transform or inspect a file while keeping the payload intact.
Two traps dominate: quality lost through repeated re-encoding, and metadata left in place after an edit. Compress once from the original, and inspect what the file still declares about you before sharing it.
Browsers, desktop tools and command-line utilities should agree on the result; a mismatch usually means a different encoding, locale or version. Open the result in a viewer you trust and check size, dimensions and, where it matters, the metadata panel rather than the file name.
Some formats are containers for other formats, so the extension alone does not tell you what is inside; when a system rejects a file, look at the actual header bytes before renaming it. Keep a copy of the input while you experiment, so a wrong setting never destroys the source.
Accepts pasted text or local .txt/.log files (text/plain) containing JVM thread dumps; outputs thread state summary, top recurring stack frames, blocked threads, and waiting-lock-to-owner correlations.
Diagnose a hung Java service by finding blocked threads and their owning locks; review top stack frames after an incident to spot common execution paths; correlate waiting threads with lock holders in deadlock investigations.
The thread dump text you paste or load from a .txt/.log file is processed by browser JavaScript and is not uploaded to KivTools.
Only text/plain thread dumps (.txt, .log) are supported; binary or non-JVM input is not analyzed and truncated dumps may yield incomplete lock correlations.
Yes. Every tool on KivTools is free, needs no account and has no usage quota. There is no paid tier hiding behind the workbench, and no email address is required to use the result.
Inside your browser. The page loads a script once and the conversion happens on your machine, which is also why the tool still works when the network drops.
Accepts pasted text or local .txt/.log files (text/plain) containing JVM thread dumps; outputs thread state summary, top recurring stack frames, blocked threads, and waiting-lock-to-owner correlations. Large inputs are usually handled without trouble, but extremely large ones are better processed in a local command-line tool.
Format first, size second: zip, tar.gz and 7z differ in compatibility as much as in ratio. Compare a small known-good sample first when the output feeds an automated pipeline.
The output is yours: no watermark, no licence tag, no attribution requirement. Check the underlying format or library licence when the result ships in a product.
The page works in any modern mobile browser, and the layout collapses to a single column on small screens. Local tools keep working offline once the page has loaded.