<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bootstrap-icons@1.11.3/font/bootstrap-icons.min.css">
FileVeda logo
Resources & Guides

Why You Should Not Paste JWTs, JSON or API Keys Into Random Online Tools

Fi FileVeda Team
November 11, 20264 Min Read

Every developer has done it. A request fails, you copy the token from the header, search for "jwt decoder", and paste it into the first result. Or you paste a 2,000-line API response into a formatter to find one field. It takes ten seconds and it works. It can also hand live credentials or customer data to a server you know nothing about.

What a JWT actually is

A JSON Web Token has three parts separated by dots: a header, a payload and a signature. The header and payload are Base64URL encoded, which is an encoding and not encryption. Anyone holding the token can read them. The signature lets a server check the token has not been altered.

Two consequences follow:

  • A JWT is a credential. Until it expires, whoever holds it can usually act as that user. Pasting a live production token into a third-party site is close to pasting a password.
  • Never put secrets in a JWT payload. It is readable by design.

What is often inside production JSON

API responses and logs regularly include email addresses, phone numbers, postal addresses, internal IDs, access tokens, signed URLs and sometimes payment details. Pasting these into an unknown service may breach your company's data handling policy and, depending on the data, privacy law.

How server-side tools can expose data

  • The input is sent to a backend for processing and may be written to request logs.
  • Some tools offer "save" or "share link" features that store your input, sometimes at a guessable public URL.
  • Third-party analytics or session recording scripts on the page can capture what you type or paste.

Most tools are run by honest people. The problem is that you cannot tell from the page which ones are careful.

How to check a tool in thirty seconds

  1. Open the browser developer tools and go to the Network tab.
  2. Paste harmless sample data and run the tool.
  3. Look for any request whose body contains your input. If there is one, the data left your machine.
  4. For a stronger test, load the page, switch the browser to offline mode, and try again. A tool that truly runs in the browser keeps working.

Safer options

  • Local commands. For JSON, the jq command line tool or your editor's format command. For a JWT, any Base64 decoder applied to the middle part.
  • Client-side web tools. FileVeda's JWT Decoder, JSON Formatter, Diff Checker and CSV to JSON Converter process input in your browser. You can confirm this with the Network tab test above.
  • Test data. Reproduce the problem with a staging token or an anonymised payload whenever you can.

Decoding is not verifying

A decoder shows you what a token claims: who the user is, when it was issued, when it expires. It does not prove the token is genuine. Verification requires the signing secret or public key and must happen on your server. Never decide that a token is trustworthy because a decoder displayed it neatly. FileVeda's decoder is an inspection tool. It shows the header, payload and expiry time so you can debug, and it leaves verification to your backend.

What to do if you already pasted a live secret

  1. Revoke or rotate it now. Invalidate the session, rotate the API key, or change the signing secret if that is what leaked.
  2. Check access logs for use of that credential from unfamiliar addresses.
  3. Tell your team. A quick message is far better than a silent risk.

Short token lifetimes limit the damage of mistakes like this, which is one reason access tokens should expire in minutes and not days.

A simple team rule

Agree on one line and put it in your onboarding notes: production tokens, keys and customer data are only pasted into tools that run locally. It costs nothing and removes a whole category of incident. More browser-based utilities are listed on the Developer Tools page, and file-level protection is covered in file encryption and checksums explained.

Share this article
FileVeda Web Utilities

Optimize and Convert Files Safely

Need to compress high-res photos, transform formats locally, or style your typography? All of our utilities run completely client-side in your web browser—your documents never touch the cloud.