UUID-/NanoID-Generator
Kodierung & Verschlüsselung · Kostenloses Online-Tool
UUID v4 und NanoID in großen Mengen generieren.
Click "Generate" to create UUID v4 identifiers...
UUID v4
Erzeugt über crypto.randomUUID() — 36 Zeichen mit Bindestrichen, RFC 4122-konform und kryptografisch zufällig.
NanoID
21 Zeichen aus einem URL-sicheren Alphabet ( A-Za-z0-9_-), kompakt und kollisionsresistent für Kurzlinks und IDs.
Sichere Zufälligkeit
Beide Generatoren nutzen die Web-Crypto-API ( getRandomValues) für unvorhersehbare, CSPRNG-würdige Entropie.
So verwendest du UUID-/NanoID-Generator
- 1Enter or paste your data into the input field.
- 2Select the desired encoding, hashing, or encryption options.
- 3Click the action button to process your data.
- 4Copy the result from the output field.
Funktionen
- ✓100% kostenlos — keine Registrierung, kein Abo, keine Werbung
- ✓Läuft vollständig im Browser — Daten verlassen niemals dein Gerät
- ✓Schnell und ressourcenschonend — sofortige Ergebnisse
- ✓Plattformübergreifend — Desktop, Tablet und Smartphone
Was ist UUID-/NanoID-Generator?
UUID (Universally Unique Identifier), defined by RFC 4122 and updated by RFC 9562, is a 128-bit identifier represented as 8-4-4-4-12 hexadecimal string (e.g., 550e8400-e29b-41d4-a716-446655440000). UUIDs are designed to be globally unique without central coordination, making them ideal for distributed systems.
Wie funktioniert UUID-/NanoID-Generator?
UUID v4 uses cryptographically secure random numbers for 122 bits (6 bits are version/variant markers). UUID v7 (RFC 9562) combines a Unix millisecond timestamp with random bits, producing time-sortable IDs that improve database index locality. Collision probability for v4 is negligible (~10^-37).
Typische Anwendungsfälle
- ✓Database primary keys — avoid auto-increment ID conflicts in sharded DBs
- ✓Distributed systems — unique IDs without central coordinator
- ✓Message tracking — correlation IDs in microservices
- ✓Session tokens — unique session identifiers
UUID v4 vs UUID v7
v4 is fully random; v7 is time-sortable (RFC 9562). v7 IDs generated close in time share prefixes, improving B-tree index locality and database write performance. v4 creates random index entries causing fragmentation. For new systems requiring database storage, prefer v7; for pure randomness (e.g., tokens), v4 is fine.
Sicherheit & Datenschutz
This tool uses the Web Crypto API (crypto.getRandomValues) for cryptographically secure random numbers. UUIDs are identifiers, NOT security tokens — they are predictable in structure. For security tokens, use a dedicated token generator with sufficient entropy.
Technische Details
Standard: RFC 4122 (original), RFC 9562 (2024 update with v6/v7/v8). Format: xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx (M=version, N=variant). v1: timestamp + MAC address. v3: MD5 hash of name. v4: random (122 bits). v5: SHA-1 hash of name. v6: reordered v1 (time-sortable). v7: Unix ms timestamp + random. v8: custom. Version bits: bits 48-51 of the UUID.
Häufige Fragen
Can UUIDs collide?
Theoretically yes, practically no. v4 has 2^122 possible values — the probability of collision among 10^18 UUIDs is ~10^-15. You are more likely to be struck by a meteor.
Should I use UUID as a primary key?
Yes for distributed systems. Prefer v7 for better index locality. v4 random UUIDs can cause index fragmentation at scale. Alternatively use snowflake IDs or ULID.
What is the difference between UUID and GUID?
GUID is Microsoft's implementation of UUID (RFC 4122). They are functionally identical. GUID typically uses mixed case; UUID standard is lowercase.
Verwandte Tools
Base64
Base64 kodieren und dekodieren mit UTF-8-Unterstützung.
URL-Encoder
URLs prozentkodieren und dekodieren.
Unicode-Konverter
Text in Unicode-Escapes umwandeln und zurück.
HTML-Entität
HTML-Entitäten kodieren und dekodieren.
Zahlenbasis-Konverter
Zwischen Binär, Oktal, Dezimal, Hex umwandeln.
Hash-Generator
MD5-, SHA-1-, SHA-256-, SHA-512-Hashes generieren.