Format JSON for API debugging
Use this workflow when an API response is hard to read, a JSON payload fails validation, or a frontend error points to malformed structured data.
Open guideWorkflow Guides
Pick a focused workflow, inspect the example, then open the matching browser tool. These guides are built for debugging API payloads, authentication tokens, spreadsheet exports, and document handoffs.
Use this workflow when an API response is hard to read, a JSON payload fails validation, or a frontend error points to malformed structured data.
Open guideUse this workflow when a login, API request, or permission check fails and you need to inspect token claims before changing auth code.
Open guideUse this workflow when an API response, webhook, cookie, or configuration value contains Base64 text that needs to be inspected before debugging.
Open guideUse this workflow when a spreadsheet export needs to become API-ready JSON, a fixture, or a structured dataset for debugging.
Open guideUse this workflow when invoices, forms, reports, or scanned pages need to be combined without sending files through an account-based document service.
Open guideUse this workflow when a vendor, GitHub release, or teammate gives you a checksum and you need to confirm that the file you downloaded has not changed.
Open guideUse this workflow when a link, redirect URL, webhook callback, or API request fails because a query parameter contains reserved characters.
Open guideUse this workflow when you need realistic unique identifiers for examples, tests, seeded records, or temporary objects without exposing production IDs.
Open guideUse this workflow when a URL needs to move from paper, a slide, a package, or a physical sign into a phone camera quickly.
Open guideUse this workflow when you need to combine image files into a PDF for sharing, archiving, submitting forms, or keeping scanned pages together.
Open guide