UUID / NanoID 생성기
인코딩 및 암호화 · 무료 온라인 도구
UUID v4 및 NanoID를 일괄 생성.
Click "Generate" to create UUID v4 identifiers...
UUID v4
crypto.randomUUID()로 생성 — 하이픈이 포함된 36자, RFC 4122 준수 및 암호학적으로 무작위입니다.
NanoID
URL 안전 알파벳(A-Za-z0-9_-)의 21자로, 짧은 링크와 ID에 적합하게 컴팩트하고 충돌 저항성이 있습니다.
안전한 무작위성
두 생성기 모두 예측 불가능한 CSPRNG급 엔트로피를 위해 Web Crypto API(getRandomValues)를 사용합니다.
UUID / NanoID 생성기 사용 방법
- 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.
주요 기능
- ✓100% 무료 — 가입, 구독, 광고 없음
- ✓브라우저에서만 실행 — 데이터는 기기를 떠나지 않습니다
- ✓빠르고 가벼움 — 즉시 결과 확인
- ✓크로스 플랫폼 — 데스크톱, 태블릿, 모바일 지원
UUID / NanoID 생성기 소개
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.
UUID / NanoID 생성기 작동 원리
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).
주요 활용 사례
- ✓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.
보안 및 개인정보
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.
기술 세부 정보
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.
자주 묻는 질문
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.