Logs and APIs often ship stringified JSON, JWTs, epoch timestamps, and local file paths. Debugging means juggling multiple tabs: unescapers, jwt.io, epoch converters, and manual path editing. This engine does it in one place, in-browser, with no data sent to any server.
Log Unpacker is a browser-based tool that decodes messy production log output into clean, readable data. It recursively unescapes nested stringified JSON (even multiple levels deep), automatically detects and decodes JWT tokens embedded in log lines, converts Unix epoch timestamps to human-readable dates, and scrubs Windows/Unix file paths to protect usernames. The result is AI-safe output you can paste directly into ChatGPT or any AI assistant for debugging help.
How it works
Unpack and Sanitize Logs in Seconds
01
Paste your log
Paste a log line, a blob of escaped JSON, or a full log file section containing stringified data.
02
Auto-detect & unpack
The tool recursively unescapes nested JSON, decodes JWTs inline (header + payload), and converts epoch timestamps.
03
Sanitize for AI
Enable path scrubbing and JWT PII masking to remove usernames and sensitive identifiers before sharing.
04
Copy AI-safe output
Copy the sanitized, readable output and paste into ChatGPT or any AI to get debugging help safely.
Use cases
When Developers Use Log Unpacker
📋
Unescape Stringified JSON
Decode nested escaped JSON strings in log files — even three or four levels deep — into readable format.
🔐
Decode JWT in Logs
Automatically detect and decode JWT tokens embedded in log output to inspect claims without a separate tool.
⏱️
Convert Epoch Timestamps
Turn 10-digit and 13-digit Unix timestamps into human-readable dates without switching to a separate converter.
🛡️
Sanitize for AI
Scrub file paths and redact JWT PII fields before pasting production logs into ChatGPT.
🐛
Debug Microservice Logs
Quickly read nested JSON payloads and auth tokens in distributed system logs without writing parsing scripts.
🔒
HIPAA/Privacy Compliance
Remove usernames and PII from log exports before sharing with third-party tools or AI assistants.
FAQ
Frequently Asked Questions
1Why do my logs show escaped quotes and backslashes instead of readable JSON?
Your logging library serialized a JSON object into a string — adding escaped quotes (\") and backslashes — before embedding it in another field. Log Unpacker recursively unescapes these strings, even when nested multiple levels deep, so you see clean readable JSON.
2How do I decode a JWT token found in log files?
Paste your log line. Log Unpacker automatically detects JWT tokens (three Base64URL parts separated by dots), decodes the header and payload, and shows them inline. Enable "Mask PII" to redact sub, name, and email fields.
3Is it safe to paste production logs into ChatGPT?
Not without sanitizing first. Logs often contain JWTs, file paths with usernames, and sensitive data. Log Unpacker produces AI-safe output with paths and tokens scrubbed — safe to paste into any AI tool.
4How are epoch timestamps converted?
Log Unpacker detects both 10-digit (seconds) and 13-digit (milliseconds) Unix timestamps and converts them to human-readable ISO date strings automatically as part of the unpacking process.
5Does Log Unpacker send my logs to a server?
No. Everything runs in your browser. No network requests, no storage, no telemetry. Safe for sensitive production logs.
6Why do my logs show escaped quotes and backslashes instead of readable JSON?
Your logging library serialized a JSON object into a string before embedding it inside another JSON field — causing the escaped quotes (\") and backslashes you see. This happens when HTTP bodies, error objects, or nested payloads are logged as strings. Log Unpacker recursively unescapes these even when nested multiple levels deep, restoring clean readable JSON.
7How do I unescape doubly or triply escaped JSON?
Log Unpacker applies recursive unescaping — it detects escaped JSON, unescapes it, checks if the result is still escaped, and repeats until the innermost value is reached. Handles 2, 3, or 4 levels of nesting automatically.
8How do I remove PII from logs before sharing with AI?
Enable "Mask PII" and "Scrub Paths" options before copying output. The tool redacts JWT identity claims (sub, name, email), sanitizes file paths, and masks common PII patterns — safe to paste into ChatGPT or any AI assistant.
9How do I convert a Unix timestamp to a readable date?
Log Unpacker automatically detects 10-digit (seconds) and 13-digit (milliseconds) Unix timestamps and converts them to ISO 8601 date strings inline. No manual identification needed — conversion happens during unpacking.
10How do I read the opaque token strings that appear in my auth-related log lines?
Those opaque strings are JWT tokens — three Base64URL-encoded parts separated by dots: header.payload.signature. They appear when Authorization headers or request bodies are logged verbatim. Log Unpacker detects and decodes the header and payload inline to show the claims (user ID, roles, expiry) without leaving your browser.
11How do I sanitize logs for an LLM or AI assistant?
Enable Mask PII to redact JWT identity claims, enable Scrub Paths to remove file system paths with usernames, then review the output for remaining sensitive data (API keys, passwords). Log Unpacker produces AI-ready output in one step.
12How do I convert multiple Unix timestamps in a log file at once?
Log Unpacker automatically detects and converts all Unix timestamps in a pasted log — both 10-digit (seconds) and 13-digit (milliseconds) epoch values — replacing them inline with ISO 8601 UTC strings. Paste your full log block and every timestamp is converted in one pass.