Payload Decoder
Decode URL/Base64 payloads, normalize JSON, and inspect timestamps from one debugging workspace.
Loading tool…
浏览器内运行这个工具能做什么
Run a visible URL-decode, Base64-to-UTF-8, and JSON-normalization pipeline from one browser workspace. Inspect each transform, detect common 10-digit, 13-digit, and ISO-style timestamp values, and copy normalized text or re-encoded handoff output without submitting the payload to a TOOLGRID processing endpoint.
The Base64 stage accepts output only when the bytes form valid UTF-8, so binary data and malformed payloads are reported instead of being presented as trustworthy text.
Timestamp detection is a review aid rather than schema validation: it recognizes common 10-digit seconds, 13-digit milliseconds, and parseable ISO-like strings, but you must confirm the field's intended timezone and business meaning.
这个工具可以完成什么
Decode a captured URL/Base64 body, validate its JSON shape, and attach a clean representation to an incident or integration ticket.
Normalize an encoded event payload and review timestamp-like fields before comparing it with a warehouse or browser trace.
Copy the exact normalized and re-encoded variants so another developer can see which transformation fixed or rejected the input.
依赖结果前需要检查什么
- Performance and maximum practical input size depend on browser memory, device speed, and the structure of the input.
- Review the generated result before replacing or publishing an original file.
如何使用
- 1
Paste the payload and choose the source chain that matches how it was encoded.
- 2
Enable JSON parsing when the normalized result should be a JSON value rather than arbitrary text.
- 3
Follow the transform pipeline and issue board; an earlier decode failure intentionally stops misleading downstream promotion.
- 4
Review detected timestamps and copy normalized text, pretty JSON, Base64 UTF-8, or URL-encoded output for the next handoff.
使用场景
Decode a captured URL/Base64 body, validate its JSON shape, and attach a clean representation to an incident or integration ticket.
Normalize an encoded event payload and review timestamp-like fields before comparing it with a warehouse or browser trace.
Copy the exact normalized and re-encoded variants so another developer can see which transformation fixed or rejected the input.
使用技巧
URL then Base64 is not equivalent to Base64 then URL. Select the format that matches the producer's documented encoding order instead of trying every option until text appears.
A parseable number or date string can still represent the wrong unit, timezone, or business field. Verify it against the producer's schema and expected event window.
This workspace promotes Base64 only as valid UTF-8 text. Images, archives, encrypted bytes, and other binary payloads need a format-specific inspector.
常见问题
Does it handle UTF-8 Base64 safely?
Yes. The workspace only promotes Base64 output when the bytes decode into valid UTF-8 text, which avoids the mojibake problem common in shallow tools.
Is this replacing the focused Base64, JSON, URL, and timestamp tools?
No. It becomes the main payload-debugging entry point, while the focused tools remain available for narrower tasks.
Which timestamp values can it detect?
It recognizes common 10-digit Unix seconds, 13-digit Unix milliseconds, and parseable date-time strings that contain a T or hyphen. Detection does not prove the field's unit or timezone semantics.
Can it decode arbitrary Base64 files?
No. The promoted Base64 output must decode as valid UTF-8 text. Binary files should be handled by an image, PDF, archive, or byte-oriented tool.
What happens when one transform fails?
The issue board names the failed stage and downstream transforms are skipped or withheld, preventing invalid intermediate data from looking like a successful result.
Is the payload sent to an API?
The decode and normalization pipeline runs in this tab. Tool code processes selected files and entered content in your browser and does not submit them to a TOOLGRID processing endpoint.
下一步常用工具
如果还需要校验、转换或复用结果，可以继续打开相近的浏览器本地工具。