Check before use
- If numeric identifiers are very large, treat them as JSON strings.
- Base64 is not encryption, so do not use it as a means of confidentiality protection.
- Encode parameter values one by one instead of the entire URL.
Prepare API test data
Check JSON syntax first, then separately compare fields and data types with the API specification. Valid syntax does not guarantee that the server will accept the request. Use strings for large numeric identifiers to avoid precision loss, and check for duplicate keys before conversion.
Choose the correct string conversion
Encode each URL parameter value separately. Encoding an entire URL with the same function also changes its separators. If an API requires Base64, check whether it expects standard Base64 or Base64URL. This site’s converter supports standard Base64 and UTF-8 text.
Verify results using test data
Use fictional test data instead of real passwords or access tokens. Encode a string, decode it again and compare it with the original to help spot truncation or double encoding. UUIDs identify records; they do not replace authorization checks or database uniqueness constraints.
Recommended operation sequence
- JSON formatter — Sort your JSON nicely and check its grammar.
- Base64 converter — Encode and decode text including Hangul.
- URL encoder — Safely convert characters in addresses.
- UUID generator — Generate as many version 4 UUIDs as needed.
Input is processed by the browser. Check out the scope and examples of each tool and use the results.