---
answer: direct
beat: dev-practices
source: 1 article · updated: November 17, 2026
---

What's the difference between PASETO's 'local' and 'public' token types?

Local PASETO tokens are symmetrically encrypted — the same key both creates and verifies them, and the payload is confidential, unreadable without that key. Public PASETO tokens are asymmetrically signed — verified with a public key, so anyone holding it can confirm authenticity and read the payload, but only the private key holder could have created it. The choice mirrors a real design decision: local tokens for confidentiality, public tokens for verifiable authenticity across multiple readers.

Answered in

JWT's Real Problem Was Never the Idea, It Was the Choices It Allows

JWT lets you choose 'none' as a signing algorithm. PASETO doesn't let you choose at all — versioned, fixed cipher suites instead of a menu of footguns.

Crashtech Editorial November 17, 2026 Development Best Practices

Read the full analysis

Other questions this article answers

More development best practices questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.