Browser JWT debuggers for a rejected test token: JWT Inspector, jwt.io, CyberChef and FusionAuth
jwt.io remains our recommended choice for a rejected test token, with a narrow lead over CyberChef. For a token that must not leave your computer, use a downloaded copy of CyberChef with the network disconnected.
jwt.io
Readable header and claims, a separate signature result, and checks for HMAC, RSA, RSA-PSS, elliptic-curve and EdDSA tokens, including keys fetched from the issuer. Its code is published and maintained.
A narrow lead: 3.20 to CyberChef’s 3.05. It does not warn that a token has expired, and Okta’s analytics tags run on the page, so use test tokens only.
Why jwt.io is our PickTeam behind jwt.io? Get your award badge
No qualifying newcomer established
JWT Inspector and AxelBase’s viewer have public source histories, but those do not establish their first public availability within the past two years.
We selected no newcomer whose dated release, fit and safety evidence met the recommendation requirements.
Who is this article for? Developers whose application or API rejected a JWT during development or testing, who want a free web tool without an account to see why, and need to know where a pasted token goes.
About 23 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
All four are free and need no account. Choose jwt.io for a rejected test token; compare what each tells you about a rejected token and what else runs on the page.
These four are free to use without an account, confirmed from their pages on November 8, 2026 and our October 19 evidence. We could not confirm the current price and access conditions for every newer alternative. jwt.io is run by Okta (Auth0) and promotes Auth0’s paid identity service on the same page. CyberChef is GCHQ’s open-source toolkit under the Apache 2.0 licence. FusionAuth’s decoder sits in its identity-service documentation. JWT Inspector publishes MIT source but does not identify a legal service operator in the evidence. None charges for the debugger.
The comparison at a glance
Compare what each tool tells you about a rejected token, which keys it checks, what else runs on the page and who runs it.
Choose jwt.io for a rejected development or test token; CyberChef suits tokens that must stay on your computer. JWT Inspector’s responsible operator and first public availability remain unconfirmed; the four columns follow score order. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | JWT Inspector | jwt.io | CyberChef | FusionAuth JWT decoder |
|---|---|---|---|---|
| Best fit | Readable claims and explicit expiry display for test tokens; responsible operator and first public availability unconfirmed | Preferred Pick: a rejected development or test token | Also consider: a token that must not leave your computer, in a downloaded copy run with the network disconnected | Checking a signature beside FusionAuth’s documentation; jwt.io is clearer for a rejected test token |
| Expired or not-yet-valid token | Explicit expired, future expiry, missing or malformed exp; no complete nbf verdict established | Dates shown in the claims table; no warning, although its changelog promises one | JWT Verify reports “jwt expired” or “jwt not active” once the signature passes | No readable dates or expiry warning found in the October 19 code examination |
| Signatures it can check | HMAC, RSA, RSA-PSS and elliptic curve; no EdDSA established | HMAC, RSA, RSA-PSS, elliptic curve and EdDSA | HMAC, RSA and elliptic curve; not RSA-PSS or EdDSA | HMAC, RSA, RSA-PSS and elliptic curve; no EdDSA established |
| Third-party scripts | No external script load in November 8 source; hosted equivalence unverified | Okta’s Adobe tag manager (Adobe data collection, 6sense fields) and OneTrust consent tool | Google Analytics on the hosted copy | Google Tag Manager / Analytics |
| Use without a network | Single HTML source can run locally; hosted equivalence unverified | Not offered (its code can be built locally) | Download a full copy to run with the network disconnected or in a closed network | No downloadable copy established |
| Who runs it | 0xelitesystem / elitesystem.ai; legal operator not established | Okta (Auth0); no jwt.io terms of use; Okta privacy policy | GCHQ, the UK intelligence and security agency | FusionAuth; identity-service vendor |
| Reader reviews | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review |
None of these tools knows your application’s expected issuer, audience, algorithm or clock, so a verified signature does not mean your server should accept the token. Use test tokens on any website. For a live token, use a downloaded copy of CyberChef with the network disconnected or decode it on your own machine. Core capabilities checked October 19, 2026; price and newcomer evidence checked November 8, 2026. Next substantive review: December 18, 2026.
All features and sources 17 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Diagnosing a rejected token
Show 8 criteria
| Feature | JWT Inspector | jwt.io | CyberChef | FusionAuth JWT decoder |
|---|---|---|---|---|
| Best fit | Readable claims and explicit expiry display for test tokens; responsible operator and first public availability unconfirmed | Preferred Pick: a rejected development or test token | Also consider: a token that must not leave your computer, in a downloaded copy run with the network disconnected | Checking a signature beside FusionAuth’s documentation; jwt.io is clearer for a rejected test token |
| What you see after pasting | Header, payload, claim notes and formatted time claims | Header and payload as JSON, or a claims table that describes each standard claim | Payload only, as JSON (JWT Decode); add steps for anything else | Header and payload as JSON |
| Expired or not-yet-valid token | Explicit expired, future expiry, missing or malformed exp; no complete nbf verdict established | Dates shown in the claims table; no warning, although its changelog promises one | JWT Verify reports “jwt expired” or “jwt not active” once the signature passes | No readable dates or expiry warning found in the October 19 code examination |
| Signature result | Separate signature result; warns on alg:none and algorithm confusion | Separate “Signature Verified” or “Invalid Signature” banner | “invalid signature” from JWT Verify | Signature validation result |
| Malformed input | Specific format/base64url/JSON errors in published source | Says which part is not valid base64url or JSON | Library errors such as “jwt malformed” | Not established |
| Signatures it can check | HMAC, RSA, RSA-PSS and elliptic curve; no EdDSA established | HMAC, RSA, RSA-PSS, elliptic curve and EdDSA | HMAC, RSA and elliptic curve; not RSA-PSS or EdDSA | HMAC, RSA, RSA-PSS and elliptic curve; no EdDSA established |
| Keys you can give it | Shared secret or PEM public key; no JWK or issuer discovery established | Secret (UTF-8 or base64url), PEM or JWK; can fetch the issuer’s published keys | Secret or PEM public key; no JWK, JWKS or issuer lookup | Secret or JWK; page also lists PEM, but its handling remains uncertain; no issuer lookup |
| Create signed test tokens | Not established | Yes, with its encoder | Yes, with JWT Sign | Not offered in the October 19 code examination |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for diagnosing a rejected token
Checked October 19, 2026 from each tool’s published code and pages: jwt.io code and v2 changelog, CyberChef JWT Verify and the library it uses, FusionAuth’s decoder (page checked November 8, 2026; capabilities from October 19), and JWT Inspector source (November 8, 2026). We pasted no token into any tool for this review. jwt.io’s missing expiry warning matches what we saw in an earlier hands-on check on October 3, 2026, before we adopted our research-only method.
Where your token goes and who runs the tool
Show 9 criteria
| Feature | JWT Inspector | jwt.io | CyberChef | FusionAuth JWT decoder |
|---|---|---|---|---|
| Cost and access | Free, no account; MIT source | Free, no account | Free, no account; downloadable copy | Free, no account |
| Where the token is processed | Inline browser processing in published source; page says nothing leaves it | In your browser, per its published code; the page makes no statement about tokens | In your browser; its README says input is never sent to its web server | Page says data never leaves the page; warns against production tokens |
| Third-party scripts | No external script load in November 8 source; hosted equivalence unverified | Okta’s Adobe tag manager (Adobe data collection, 6sense fields) and OneTrust consent tool | Google Analytics on the hosted copy | Google Tag Manager / Analytics |
| Token in the address bar | No token URL or history persistence in source examined | Only if you open a link with #token= | Copied after # by default; switch off in Options | Not established |
| Use without a network | Single HTML source can run locally; hosted equivalence unverified | Not offered (its code can be built locally) | Download a full copy to run with the network disconnected or in a closed network | No downloadable copy established |
| Source code and licence | Published, MIT; full single HTML file readable | Published, Apache 2.0 | Published, Apache 2.0 with Crown copyright | Documentation source published; licence not established |
| Who runs it | 0xelitesystem / elitesystem.ai; legal operator not established | Okta (Auth0); no jwt.io terms of use; Okta privacy policy | GCHQ, the UK intelligence and security agency | FusionAuth; identity-service vendor |
| Maintenance in 2026 | Human changes through September 30, 2026; no deployed update promise | Code updated through September 2026 | At least ten releases, latest 11.5.0 on September 18 | Decoder-specific maintenance not established |
| Security record | July fixes for malformed input and stale verification results visible in source; no applicable serious current advisory established | No jwt.io advisory found; Okta’s 2023 support-system intrusion exposed customers’ session tokens | Six 2026 advisories, three of them script injection, all fixed by 11.5.0 | No decoder-specific security finding established |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for where your token goes and who runs the tool
Pages, scripts and security headers as served on October 19, 2026; jwt.io’s Adobe analytics change; Okta privacy policy; CyberChef README, address-bar code, releases and advisories; Okta’s 2023 root cause analysis. A script we could see is not proof of what it records; we did not monitor any page’s network traffic for this review.
What matters when choosing
jwt.io is our Practical Pick for working out why your application rejected a development or test token. It is free and needs no account. Paste a token and it decodes the header and claims, describes each standard claim and shows time claims as dates, and reports the signature result separately. It verifies HMAC, RSA, RSA-PSS, elliptic-curve and EdDSA signatures from a secret, a PEM key or a JWK, and for a token from an identity provider it can fetch the public keys the issuer publishes. Its code is published under the Apache 2.0 licence, and Okta’s Auth0 team was still updating it in September 2026. jwt.io, published code
Its lead is narrow. On the four criteria we fixed before scoring, jwt.io scored 3.20 out of 5 and CyberChef 3.05, less than one scoring step apart. Between jwt.io and CyberChef, giving more weight to where a pasted token goes would put CyberChef first. Two jwt.io limits matter for this job. It does not tell you a token has expired: its v2 changelog says the decoder warns about expired tokens, but its published code defines no such message, so you compare the expiry date with the time yourself. “Valid JWT” means the token is well formed and “Signature Verified” means the key matched; neither means your application should accept it. And the page loads Okta’s marketing and analytics tags alongside your token, so use it for test tokens only. Claim display code, unchanged since June 2025, v2 changelog
Use CyberChef when a token must not leave your computer. GCHQ’s open-source toolkit says it never sends your input to its web server, and you can download a full copy from its page and run it with your network switched off. Its JWT Verify step names the problem when a check fails: “invalid signature”, “jwt not active” or “jwt expired”. It is a general data toolkit, though. You add each step yourself, it checks only HMAC, RSA and elliptic-curve tokens with PEM keys, and its decoder shows only the payload, with raw timestamps. On the hosted copy, use a test token or switch off the option that copies your input into the address bar. CyberChef, README
Keep live tokens out of every website, including these. A JWT is usually a bearer credential: whoever holds a valid one can use it until it expires, and its payload is readable without any key. Customer session tokens have been stolen even from Okta, which owns jwt.io. In October 2023 an attacker reached its support system, took files customers had uploaded, some of them containing session tokens, and used those tokens to hijack sessions at five customers. In November 2025, researchers at watchTowr reported retrieving more than 80,000 saved entries from two popular code-formatting websites, including passwords, access tokens and private keys that people had pasted. For a production token, use a downloaded copy of CyberChef with the network disconnected, or decode it on your own machine with your JWT library or a command-line tool such as jwt-cli. jwt-cli is MIT-licensed and packaged for Homebrew, Cargo and Scoop, but its last release was in November 2024, its verify mode allows about 16 minutes’ grace after expiry, and it does not check audience. Okta root cause analysis, November 3, 2023, Help Net Security, November 25, 2025, jwt-cli, jwt-cli verify settings
No Rising Star selected. We did not establish a first public release within the past two years for an otherwise suitable independent newcomer. JWT Inspector and AxelBase’s viewer have source histories, but those do not establish when the tools first became publicly available. JWT Inspector history, AxelBase history, checked November 8, 2026.
We could not confirm the current price and access conditions for every newer alternative.
None of these tools knows your application’s rules. The JWT standard defines the iss, aud, exp and nbf claims, and the JWT best-practice guidance tells verifiers to check the algorithm, the issuer and, where a token could serve more than one recipient, the audience. When a token is rejected, compare its iss, aud and alg with your server’s settings, and its exp and nbf with your server’s clock. RFC 7519, RFC 8725
JWT Inspector
Alternative · readable claims and expiry display
JWT Inspector combines readable claim notes, an explicit expiry display and signature checks for test tokens. Its public source is readable; its responsible service operator and first public availability remain unknown.
Reasons to choose it
- Header and claim notes with readable dates and expiry status
- HMAC, RSA, RSA-PSS and elliptic-curve checks using Web Crypto
- Single HTML source under MIT, with no token-sending request in the file examined
What to watch
- No legal operator or privacy policy identified in the evidence
- No JWK, issuer-key discovery or EdDSA support established
- Hosted code equivalence and first public availability unconfirmed
JWT Inspector is a free, MIT-licensed browser tool from 0xelitesystem. It displays the header, payload and claim notes, formats time claims and distinguishes a missing or malformed expiry from an expired token. Its published single HTML file uses the browser’s Web Crypto API for HMAC, RSA, RSA-PSS and elliptic-curve signature checks with a shared secret or PEM public key. It flags unsigned alg:none tokens and warns about algorithm confusion. We did not establish EdDSA, JWK input, issuer-key discovery or signing support. It does not know your application’s expected issuer or audience. Public app, source, checked November 8, 2026.
The source we read has inline scripts, no external script loading or token-sending request, and stores only the theme preference. The page says nothing leaves it. That is useful source transparency, but we did not compare the deployed app byte for byte with the repository or monitor its traffic. Keep live tokens out of it. Its footer links elitesystem.ai but supplies no legal operator or privacy policy. The repository has human changes through September 30, 2026; July changes describe fixes for malformed input and stale verification results, visible in the current source. Those are maker records, not our product tests. Repository, history, checked November 8, 2026.
Read the full JWT Inspector analysis and sources
Choose it for readable claim notes and an explicit expiry display on test tokens when the documented algorithms cover your task. Choose another route when you need an identified service operator, issuer-key discovery or a tool for live credentials. Its earliest recorded source commit is June 11, 2026; first public availability remains unknown.
Used JWT Inspector? Share your experience to help other readers choose.
jwt.io
Preferred Pick · a rejected development or test token
Choose jwt.io to see why a development or test token was rejected: readable claims, a separate signature result and support for the common signing keys. Check the expiry date yourself, and keep live tokens off the page.
Reasons to choose it
- Header and claims with descriptions and readable dates
- Checks HMAC, RSA, RSA-PSS, elliptic-curve and EdDSA signatures, and can fetch the issuer’s keys
- Published Apache 2.0 code, updated in September 2026
What to watch
- No expiry warning, although its changelog promises one
- Okta’s marketing and analytics tags run on the same page
- “Valid JWT” means well formed, not accepted by your application
Paste a token and jwt.io decodes the header and the payload. Its Claims Breakdown view describes each standard claim and shows exp, nbf and iat as dates beside the raw numbers. Separate banners say whether the token is well formed and whether the signature matched, and malformed input gets a specific message, for example when a part is not valid base64url or the payload is not a JSON object. For HMAC tokens you enter the secret as UTF-8 or base64url; for RSA, RSA-PSS, elliptic-curve and EdDSA tokens you paste a PEM or JWK public key, or let jwt.io find the issuer’s published keys from the token’s iss claim. That lookup goes from your browser to the issuer, not to jwt.io. Its encoder creates signed test tokens. We found no support for encrypted tokens (JWE), and you cannot give it the issuer or audience your application expects. Published code, commit history
Expiry is the gap for this job. The v2 changelog lists an expiry warning among the new decoder’s features, and the published component that displays claims contains a check for a past exp. But the message that check would show is not defined, so no warning appears; the file has not changed since the June 2025 v2 release. In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, we pasted invented HS256 test tokens into jwt.io as it was served that day. A correctly signed token whose exp had passed showed “Valid JWT” and “Signature Verified” with no expiry warning in the default view, while an altered payload and a wrong key failed the signature check as they should. That check covered one day and one algorithm and did not decide this recommendation. Claim display code, v2 changelog, earlier check record, October 3, 2026
Read the full jwt.io analysis and sources
Its published code decodes and verifies in your browser with the open-source jose library. The current page makes no statement about tokens, though; it says only that a private key entered for signing “never leaves your browser”. The older site’s statement that jwt.io does “not record tokens” no longer appears. The page also loads Okta’s tag manager and a OneTrust consent tool. The tag configuration served on October 19, 2026 uses Adobe’s web data collection and includes fields for 6sense company identification and Google Analytics cookie values; Okta added the Adobe script in October 2025. The footer says Okta may share personal information with advertising partners through cookies. The token boxes carry a setting that tells the Heap analytics service to ignore them. It was first added in May 2020, after a user reported that text selected on the page, which could include parts of a token or secret, was being sent to Heap; the maintainers fixed it the same day. We found no report that the current page sends tokens anywhere, and we did not test it. Adobe script component, Adobe analytics change, October 2025, Heap report, May 5, 2020
jwt.io can preload a token from the part of a link after #token=, which browsers do not send to the web server. The page carries a notice recommending that form over the older ?token= query parameter; its maintainers wrote in 2024 that passing tokens that way had raised privacy concerns. Maintainer plan, July 19, 2024
The page says “Presented by Auth0” and carries an Okta copyright; Okta completed its purchase of Auth0 in May 2021. jwt.io has no terms of use of its own. Its footer links Okta’s privacy policy, last updated in June 2026, which covers cookies and Google Analytics and says some sharing with advertising partners may count as a “sale” or “sharing” under California law. Okta’s security record matters when you decide what to paste on its sites. Besides the 2023 support-system intrusion described above, attackers copied Okta’s source code repositories in December 2022; Okta said Auth0 products were not affected. In November 2024 Okta disclosed a flaw in its AD/LDAP delegated sign-in that, under specific conditions, accepted a cached login for usernames of 52 characters or more; it was fixed on October 30, 2024. Okta’s advisory list has no entry for jwt.io, and we found no reported incident involving jwt.io itself. Auth0 acquisition, May 3, 2021, Okta privacy policy, BleepingComputer, December 21, 2022, AD/LDAP advisory, November 1, 2024, Okta security advisories
Choose something else when you need an explicit expiry verdict, work with encrypted tokens, or hold a token that still works.
Used jwt.io? Share your experience to help other readers choose.
CyberChef
Also consider · a token that must not leave your computer
Choose CyberChef for a token too sensitive for a website: download a copy from its page, run it with your network off, and use JWT Decode and JWT Verify.
Reasons to choose it
- Downloadable copy for use with the network disconnected or in a closed network
- JWT Verify names an expired, not-yet-valid or wrongly signed token
- Frequent 2026 releases, with security advisories published and fixed
What to watch
- The hosted copy loads Google Analytics and copies your input into the address bar by default
- HMAC, RSA and elliptic-curve keys in PEM only; no JWKS
- The decoder shows only the payload, with raw timestamps
CyberChef is GCHQ’s open-source web app for encoding, decoding and analysing data, released under the Apache 2.0 licence with Crown copyright. Its README says that none of your input “is ever sent to the CyberChef web server” and that you can download a full copy to run locally or inside a closed network; the download link is on the page itself. Version 11.5.0, released September 18, 2026, was one of at least ten releases in 2026. README, releases
Three operations handle JWTs. JWT Decode shows the payload, not the header, as JSON, with times as raw numbers unless you add a timestamp-conversion step. JWT Verify takes a secret or a PEM public key and supports the HS, RS and ES algorithm families, not RSA-PSS or EdDSA; it does not read JWKs or fetch an issuer’s keys. JWT Sign creates test tokens. Verify relies on the jsonwebtoken library’s default checks, which test the signature first and then the token’s time limits, so its error names the cause: “invalid signature”, “jwt not active” or “jwt expired”. It does not check issuer or audience. JWT Verify source, jsonwebtoken check order
Read the full CyberChef analysis and sources
The hosted copy at gchq.github.io loads Google Analytics. By default CyberChef also copies your input, base64-encoded, into the address bar after the # sign whenever it is under 51,200 bytes, which covers any ordinary token. Browsers do not send that part to the web server, but scripts on the page can read it, and we could not establish whether Google Analytics records it. Untick “Update the URL when the input or recipe changes” in Options before pasting, or use a downloaded copy with the network disconnected. Input handling source, hosted app
CyberChef published six security advisories in 2026, all fixed by version 11.5.0. Three were script-injection flaws, fixed in 11.0.0, 11.2.0 and 11.4.0; on a page where you paste credentials, such a flaw could let a crafted link run code. Another, rated high and fixed in 11.5.0, let a shared link make CyberChef send web requests from the visitor’s browser. The hosted copy was on 11.5.0 when we checked; a downloaded copy has to be replaced by hand. Security advisories, shared-link advisory, September 18, 2026, CVE-2026-42615
Choose something else when you want readable claims at a glance, need RSA-PSS, EdDSA or JWKS support, or do not want to assemble the steps yourself.
Used CyberChef? Share your experience to help other readers choose.
FusionAuth JWT decoder
Alternative · a signature check with your own key
Use FusionAuth’s decoder for a quick signature check beside its identity documentation; jwt.io gives a clearer view of a rejected test token.
Reasons to choose it
- Header and payload as JSON
- HMAC, RSA, RSA-PSS and elliptic-curve signature checks
- Page warns against production tokens
What to watch
- No readable dates or expiry warning in the October 19 code examination
- No issuer-key discovery
- Google Analytics on the page examined October 19
FusionAuth’s free web decoder shows a JWT’s header and payload and checks its signature using a supplied key. Its page says the data never leaves the page and warns against pasting production tokens. The October 19 code examination found HMAC, RSA, RSA-PSS and elliptic-curve verification, without issuer-key discovery or readable time claims. The current page still offers the header, payload and signature-validation fields. JWT decoder, checked November 8, 2026
It scored 2.70 against jwt.io’s 3.20. It has no documented expiry warning, cannot fetch the issuer’s keys and loaded Google Analytics when we examined the page on October 19. The page says it accepts a secret, PEM or JWK; our code reading established secret and JWK handling, so PEM support remains uncertain. It suits someone who already uses FusionAuth’s documentation and wants a quick signature check, but supplies no decisive advantage over jwt.io for this reader.
Read the full FusionAuth JWT decoder analysis and sources
Choose something else when you need readable claim dates, an expiry verdict or automatic issuer-key discovery.
Used FusionAuth JWT decoder? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
We found no representative survey of developers’ experience with these tools, so project records are the main public view. jwt.io’s maintainers wrote in July 2024 that the old debugger mixed decoding, signing and verification in one widget, surfaced some errors poorly and drew privacy concerns by accepting tokens in a link’s query string. The v2 changelog that followed promised separate widgets, readable times and an expiry warning. In May 2020 a jwt.io user reported that text selected on the page was being sent to Heap analytics, although the site then said it did not record tokens. The maintainers excluded the token editor from Heap the same day, said the captured text was not used and said they would have it erased; the thread does not confirm that it was. Maintainer plan, v2 changelog, Heap report
At least one of CyberChef’s 2026 advisories came from an outside researcher: a report received on June 5, 2026 was fixed in version 11.2.0, released June 17. Our searches found no comparable public record for jwt.ms. We did not use popularity, star ratings or unverified social posts to choose a Pick, and a search that finds nothing is not proof that nothing exists.
How we researched
This is public-source research. For this review we did not paste a token into any of these tools, install anything, create accounts or contact the makers. No maker supplied access or payment, and our links carry no affiliate tracking. We first compared jwt.io, WorkOS’s debugger and a newer independent debugger on October 3, 2026, partly through a hands-on check with invented tokens. We report what that check showed for jwt.io only as dated history, because we have since adopted a research-only method. On October 19, 2026 we rechecked every material claim against each tool’s published code and documentation, the pages and security headers as served that day, terms and privacy policies, release histories, security advisories, the operators’ incident records and independent reporting.
We wrote this for a developer whose application or API rejected a JWT during development or testing and who wants a free web tool, without an account, to see why, and to know where the pasted token goes. Before scoring, we fixed four criteria and their weights: how clearly the tool diagnoses the token (30%); where the token goes and how open the tool is about it (30%); algorithm and key support (15%); and who runs it, with its terms, maintenance and security record (25%). Each tool also had to be free without an account and have terms that allow use at work. JWT Inspector scored 3.53, jwt.io 3.20, CyberChef 3.05 and FusionAuth 2.70. JWT Inspector’s responsible service operator and first public availability remain unconfirmed. jwt.io remains our recommendation for test tokens. Between those two recommendations, weighting where the token goes at 40% would put CyberChef narrowly ahead, which is why we name it for sensitive tokens.
We revisited newcomers on November 8, 2026 through GitHub’s JWT debugger directory and repository search, alongside the earlier candidate list and the makers’ current documentation. JWT Inspector’s earliest recorded source commit is June 11, 2026, not a confirmed initial public release. Its current app and source support the comparison above. AxelBase’s viewer now has a readable public decoder with expiry badges and an MIT licence claim, but its first public availability is also unknown. WorkOS’s March 2026 launch comes from an established identity vendor and its website terms restrict commercial use. TokenPrism still names no operator or linked source against which to check processing. None qualifies for our Rising Star recommendation. JWT Inspector history, AxelBase app, WorkOS terms, TokenPrism privacy explanation, checked November 8, 2026.
The other scored browser tools follow outside the four-column chart: Castov 2.55; AxelBase JWT Viewer 2.43; jwt.ms 2.30; IT-Tools 2.28; token.dev 2.20. Public source and processing statements do not establish what a hosted deployment does. We could not establish these products’ first public availability within the newcomer window. jwt.ms remains useful for Microsoft Entra claim notes, but does not verify signatures and names no operator. Castov, AxelBase viewer, jwt.ms, checked November 8, 2026.
ToolAdda, DevToolbox, JSONFormatter, Code Beautify and ufreetools remain unscored because their available documentation does not establish the processing, operator or current JWT capabilities needed for complete scores. We do not recommend them on that evidence. ToolAdda documentation, DevToolbox repository, checked November 8, 2026.
IT-Tools’ JWT parser displays the header and payload with claim labels and a readable issued-at date, but offers no signature check on its page. It scored 2.28, below jwt.ms’s 2.30: its named maintainer and published GPL code help accountability, while the last listed release is from October 2024 and current maintenance is uncertain. token.dev now displays readable issue and expiry times; it scored 2.20 on the capabilities we could substantiate, with its full algorithm list and maintenance unresolved. It comes from Okta’s developer team, the same company as jwt.io, and therefore cannot be our newcomer recommendation. Command-line tools such as jwt-cli and desktop toolkits remain a different route for live tokens; extensions require installation and security-testing suites serve a different job. CodeBeautify’s homepage links a JWT decoder, but we could not establish its current capabilities or price; JSONFormatter’s decoder page could not be read. Their current JWT features and data-handling limits remain unconfirmed. IT-Tools parser, repository, releases, token.dev, CodeBeautify, checked November 8, 2026.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| jwt.io | Published code and change history, the page and its tag configuration as served, maintainer issues, Okta privacy policy, Okta incident reports and advisories, earlier check record (October 3, 2026). | What Okta’s tags record on this page, whether the expiry warning will be restored, how long the tool stays free and unchanged. |
| CyberChef | README, JWT operation source, address-bar handling source, release notes, security advisories, the hosted page. | Whether Google Analytics on the hosted copy records the part of the address after #; how current a downloaded copy is. |
| FusionAuth | Decoder page checked November 8, 2026; October 19 code examination. | PEM handling, maintenance of the decoder and whether its analytics receives token data. |
| Newcomers | GitHub directory and repository search; JWT Inspector source, app, history, issues and advisories; AxelBase app, repository and package file; other named repositories, checked November 8, 2026. | First public availability, hosted-source equivalence and service legal identity; incomplete documentation for the unscored tools. |
| jwt.ms | The page and its script as served, Microsoft identity documentation. | Who runs it, whether any privacy policy or terms apply, how it is maintained. |
None of this establishes that a tool behaves as its code or documentation says in every browser, or that a page carries no tracking we could not see. Next substantive review is due December 18, 2026, or sooner if jwt.io restores its expiry warning or changes its tags, or a security matter arises. Found a change? Contact the editors.
Sources and evidence
Sources were checked October 19, 2026 unless another date is given. Published code shows how a tool is built; it does not prove what a hosted page runs on a given day. Makers’ pages establish what the maker says.
- jwt.io: debugger; published code, Apache 2.0; commit history; claim display code, June 2025; Adobe script component; Adobe analytics change, October 2025; maintainer plan, July 19, 2024; v2 changelog; Heap report, May 5, 2020; Okta privacy policy, last updated June 2026.
- Okta: Auth0 acquisition, May 3, 2021; support-system root cause, November 3, 2023; investigation closure, February 8, 2024; KrebsOnSecurity, November 29, 2023; BleepingComputer, December 21, 2022; AD/LDAP advisory, November 1, 2024; security advisories.
- CyberChef: hosted app; repository and README; JWT Verify source; input handling source; releases; security advisories; shared-link advisory, September 18, 2026; reflected script-injection advisory, August 29, 2026; CVE-2026-42615; jsonwebtoken verification order.
- jwt.ms: decoder; Microsoft access-token documentation.
- Local route: jwt-cli; jwt-cli verify settings.
- Newcomers and tools set aside: WorkOS debugger; WorkOS launch, March 24, 2026; WorkOS website terms, last updated October 29, 2020; FusionAuth JWT decoder; token.dev.
- Standards and context: RFC 7519; RFC 8725; Help Net Security on watchTowr’s research, November 25, 2025; earlier check record, October 3, 2026.
This is a researched comparison, not a product review. Method: evidence standard, editorial picks.