🛠️ Developer Tools
JSON-Formatter, URL-Encoder, Hash-Generator und mehr
Verschönere, validiere und formatiere JSON. Kostenlos JSON-Beautifier, Validator und Pretty Printer.
Tool öffnen →Kodiere oder dekodiere URL-Strings. Kostenloses URL-Encoder und Decoder Tool.
Tool öffnen →Erzeuge SHA-1, SHA-256, SHA-512 und MD5 Hashes online.
Tool öffnen →Erzeuge starke, sichere, zufällige Passwörter auf Anfrage.
Tool öffnen →Teste und debugge reguläre Ausdrücke mit Echtzeit-Matching und Erfassungsgruppen.
Tool öffnen →Erzeuge zufällige UUID v4 Identifier. Generiere bis zu 100 UUIDs im Batch.
Tool öffnen →Konvertiere Unix-Timestamps in Daten und zurück. Epoch-Konverter mit Zeitzone-Unterstützung.
Tool öffnen →Erstelle und erkläre Cron-Zeitplan-Ausdrücke visuell. Sehe nächste Ausführungszeiten.
Tool öffnen →Minifiziere HTML, CSS und JavaScript. Sehe Größeneinsparungen sofort.
Tool öffnen →CIDR-Notation, Netzwerkadresse, Broadcast und Hostbereiche berechnen.
Tool öffnen →Erstellen Sie schöne CSS-Verläufe mit einem visuellen Editor. CSS-Code kopieren.
Tool öffnen →Erstellen Sie CSS Box-Schatten visuell mit Live-Vorschau. Code kopieren.
Tool öffnen →Umrechnung zwischen Binär, Dezimal, Oktal und Hexadezimal.
Tool öffnen →Umrechnung zwischen Bytes, KB, MB, GB, TB und weiteren Datengrößen.
Tool öffnen →JSON Web Tokens dekodieren und inspizieren. Header, Payload und Signatur anzeigen.
Tool öffnen →Vergleichen Sie zwei Texte nebeneinander und sehen Sie die Unterschiede.
Tool öffnen →The utilities you reach for a dozen times a day and never want to think about — formatting a blob of JSON, decoding a token to see why auth is failing, generating a UUID, working out what a cron expression actually means.
All of them run in your browser. That is the point: pasting a production JWT, an internal API response or a customer record into a random web form is a habit worth breaking, and here there is no server to send it to. Open the network tab and check.
Which tool do I want?
| If you… | Use |
|---|---|
| You have unreadable JSON and want it formatted or validated | JSON-Formatter |
| Auth is failing and you need to see what is in the token | JWT-Decoder |
| You are writing a pattern and want to test it live | Regex-Tester |
| You need a strong password or an API key | Passwort-Generator |
| A cron line is opaque and you want it in English | Cron-Ausdruck-Generator |
| You are planning subnets or checking whether an IP is in range | Subnetz-Rechner |
| You have a Unix timestamp and need a date | Zeitstempel-Konverter |
| You want to see exactly what changed between two files | Text vergleichen / Diff |
Decoding a JWT is not verifying it
The JWT decoder here shows you the header and payload, because both are plain base64url — anyone holding the token can read them. What it does not do is check the signature, and that distinction has caused real security incidents.
A decoded token showing admin: true tells you what the token claims, not whether that claim is true. Verification means recomputing the signature with the issuer's key and confirming it matches, then checking the expiry, the issuer and the audience. That has to happen on your server, with a library, every time.
So: never put secrets in a JWT payload, since it is readable by design. And never trust a claim you have only decoded. The decoder is a debugging aid for working out why auth is behaving oddly — it is not an authorisation check.