Java Exception and Stack Trace Formatter
java.lang.IllegalStateException: Could not initialize service
at com.example.app.ServiceBootstrap.start(ServiceBootstrap.java:42)
at com.example.app.Main.main(Main.java:11)
Caused by: java.sql.SQLException: Connection timeout
at com.example.db.Client.connect(Client.java:83)
at com.example.db.Client.open(Client.java:42)
Caused by: java.net.SocketTimeoutException: Connect timed out
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Native Method)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597)
... 2 moreFAQ
Prettify rewrites the parsed exception chain back into a clean, readable Java stack trace with normalized line breaks, Caused by: sections, and ... n more lines. Tree table mode turns the same trace into expandable rows so you can inspect each exception node, its message, and its individual frames in a single table.
They only affect the tree table view. Top level first follows the original log order, starting with the outer exception and then walking down through each Caused by: section. Root cause first reverses that display order so the deepest underlying exception appears first, which is often faster when you are debugging nested failures.
Yes. The parser normalizes escaped \n/\t sequences, some condensed single-line traces, pipe-separated traces, and JSON input that contains stackTrace entries. It then converts that input into the same prettified or tree-table output.
Yes. Native frames and unknown-source frames are detected and labeled explicitly, and collapsed parent-frame markers like ... 2 more are preserved as omitted-frame counts instead of being dropped.
It formats the stack trace text you paste, but it does not deobfuscate renamed classes or recover missing source maps. Parsing, prettifying, regex frame filtering, and tree rendering all happen locally in your browser, so your stack trace is not uploaded by this tool.
