Unwrap Nested Base64

Sometimes data is Base64-encoded more than once (API gateways, copy-paste through another encoder, or an LLM “helpfully” re-encoding). This tool peels layers until the payload is plain text or binary—and shows each step.

When nested Base64 shows up

  • An API already returned Base64 and a client encoded it again
  • An LLM “encoded for safety” on top of existing Base64
  • Config pipelines that Base64-wrap secrets multiple times

Stop when the next layer is no longer valid Base64 text, or when decoded bytes look binary (images, ZIP, PDF).

常見問題

Why would Base64 be encoded twice?

Common causes: encoding a value that was already Base64, wrapping binary in JSON as a string then encoding again, or an LLM applying Base64 on top of existing Base64.

How many layers do you peel?

Up to a safe limit (about 8). If every layer is still valid Base64 of printable text, we stop when the next decode would not look like Base64 text.

相關工具與指南

留言 (0)

對「Unwrap Nested Base64」有問題、想法或發現錯誤嗎?歡迎留言、為工具評分或回覆他人。

目前還沒有留言,歡迎搶先分享您的意見!

發表留言

為此工具評分:
Esc
↑ ↓ 移動↵ 開啟Esc 關閉