zippydevtoolsJSON
JSON Log Parser
Extract, unescape, and format JSON trapped inside CloudWatch, Lambda, Docker, and API log strings.
- Parsing runs in the browser and does not require a dedicated backend to interpret the input.
- Logs can contain tokens, cookies, emails, or identifiers. Review and mask sensitive data before sharing.
Process the input to see the result here.
Paste logs with escaped JSON, extract the payload, and get readable formatted output for debugging errors, requests, and structured messages.
When to use
Use it when CloudWatch, Lambda, Docker, or API logs show JSON as an escaped string instead of a readable object.
Input
Paste the full log line or only the escaped JSON string. Enable extraction for prefixed logs and nested parsing when internal fields are escaped JSON too.
Output
The output is formatted JSON. Review sensitive fields before copying the result into tickets, chats, or documentation.
- Paste the log line or escaped JSON string into the input field.
- Keep extraction enabled for logs with timestamps, levels, or prefixes.
- Enable nested JSON parsing to convert text fields that contain another JSON payload.
- Run the parser, review the formatted JSON, and copy only the fields you need.
- Debug a CloudWatch error: Turn escaped Lambda payloads into readable JSON so requestId, statusCode, message, and stack context are easier to inspect.
- Review API payloads from logs: Extract the JSON object from a prefixed log line and validate fields before opening the formatter or validator.
- Truncated logs: When the line ends before closing quotes, braces, or brackets, the parser returns an error and the log must be captured completely.
- Sensitive data: Logs can include tokens, emails, documents, or customer payloads. Review and mask sensitive fields before sharing output.
- Non-JSON strings: Plain text messages are not converted. The tool expects valid JSON, either direct or escaped.
Extract JSON from a CloudWatch line
Input: 2026-06-25T10:00:00Z INFO {\"level\":\"error\",\"requestId\":\"abc\"}
Output: Formatted JSON object with level and requestId.
Parse nested JSON in a message field
Input: {"message":"{\"error\":\"timeout\",\"code\":504}"}
Output: message converted into a readable JSON object.
What is JSON Log Parser for?
It extracts JSON from log lines, removes common string escaping, and formats the result for debugging structured messages.
Does it work with CloudWatch logs?
Yes. Paste the full CloudWatch line and keep JSON extraction enabled when a timestamp, log level, or prefix appears before the payload.
What happens to JSON inside fields like message?
When nested JSON parsing is enabled, string fields that contain valid JSON are converted into readable objects or arrays.
Does the tool repair invalid JSON?
No. It unescapes and extracts valid JSON, but broken quotes, braces, brackets, or truncated logs must be fixed at the source.
Are my logs sent to a server?
No through the tool execution. Parsing runs in the browser; still review internal policies before pasting logs with tokens or personal data.
How do I use this tool safely?
Enter the requested input, run the tool, and review validation messages or warnings before copying the result.
Which inputs and outputs should I check?
Use the fields, formats, and limits described in the tool interface; review the output before applying it to critical workflows.