Example Walkthrough
Base64 to text
Input: VGVzdCBkYXRhIGZvciBCYXNlNjQ=
Action: Use Base64 → Text in the Text workspace.
Output: Test data for Base64
Use Base64 in API Debugging
When request or response payloads include Base64 fields, this workflow helps you quickly verify encoding direction, readability, and transport safety.
Suitable Input Types
- Raw Base64 fields copied from API request or response payloads
- Plain text snippets that must be encoded before sending
- JSON payload fragments where one field contains encoded content
Step-by-Step Workflow
- Open Text workspace and paste the target field from your payload.
- Switch mode based on direction: Base64 → Text for inspection, Text → Base64 for rebuilding.
- Copy normalized output back into your API request, test script, or docs.
Common Issues in This Scenario
Copied value contains hidden spaces or line breaks
Trim accidental whitespace before decoding. Wrapped lines from logs often break decoding.
You encoded an already encoded field
If output looks unreadable after decoding once, verify whether source data was double-encoded in upstream logic.
Padding mismatch between systems
Some systems omit trailing "=". Check compatibility expectations before comparing values.