Skip to content
UUID App
Contact
UUID App

UUID v5 Generator

Pick a namespace and type a name. The same name always gives the same ID. Click Copy to use it.

Your UUID v536 characters
xxxxxxxx-xxxx-5xxx-8xxx-xxxxxxxxxxxx
  • Free, no sign-up
  • Follows the official RFC 9562 standard

Free UUID generator: v4, v7, GUID and more

Make UUID v5s from a list

Paste up to 10,000 names and get one UUID v5 for each, using the namespace above. Three quick steps.

Pick a file type
Check and download

What is a UUID v5?

A UUID v5 is an ID made from a name. Give it the same namespace and name, and you get the same ID every time, on any computer.

Version 5 runs a SHA-1 hash over two things: a namespace UUID and your name. The namespace says what kind of name it is, such as a domain (DNS) or a web address (URL). The hash is cut down to 128 bits and 6 of them are set to mark the version and variant.

Nothing is random and nothing is stored. That makes v5 handy when two systems must agree on an ID without talking to each other, or when you want to turn an existing key, like an email or a URL, into a UUID.

What a UUID v5 looks like

Here is the ID for the name you typed, split into its parts. Change the name and watch it change.

  • The 5 means version 5. It is always in this spot.
  • This digit is always 8, 9, a or b. It marks the standard layout.
  • Everything else is hash bits: 122 bits taken from the SHA-1 hash of the namespace and name. They look random, but they are fixed for that name.
Need 10,000 UUIDs? Export to CSV, JSON or SQL. Try it free

When to use UUID v5

Good for

  • Stable IDs for URLs, domains or file paths
  • Turning an existing key, like an email, into a UUID
  • Two systems that must reach the same ID on their own
  • Re-running imports without creating duplicate rows

Pick something else when

  • You just need a new, unique ID: UUID v4
  • IDs must sort by time, like big database keys: UUID v7
  • An older system expects MD5-based IDs: UUID v3
  • The name is secret, like a password or token: v5 is not a safe way to hide it

Make a UUID v5 in code

import { v5 as uuidv5 } from 'uuid';

const id = uuidv5('example.com', uuidv5.DNS);
console.log(id); // cfbff0d1-9375-5685-968c-48ce8b15ae17

Uses the uuid package from npm. Browsers and Node.js have no built-in v5.

UUID v5 vs other versions

VersionMade fromSame input, same IDSorts by time
v5 (this page)SHA-1 hash of a nameYesNo
v3MD5 hash of a nameYesNo
v4Random bitsNoNo
v7Time + randomNoYes
Need 10,000 UUIDs? Export to CSV, JSON or SQL. Try it free

Questions people ask

Will I get the same UUID v5 in every language?

Yes, as long as the namespace and the name bytes match. Watch for small differences like a trailing slash, letter case or extra spaces. "Example.com" and "example.com" give different IDs. Java and .NET have no built-in v5, so use a library there.

Which namespace should I pick?

Use DNS for domain names, URL for full web addresses, OID for ISO object IDs and X.500 for directory names. For your own kinds of names, make one random UUID v4, keep it fixed, and use it as a custom namespace.

SHA-1 is broken. Is UUID v5 still safe to use?

For IDs, yes. The attacks on SHA-1 matter for signatures and passwords, not for naming things. Just do not treat a v5 as a secret: anyone who can guess the name can work out the ID.

Can I get the name back from a UUID v5?

No. The hash only goes one way. But if the name is easy to guess, someone can try names until one matches, so keep private data out of v5 names.

Should I use v5 or v3?

Use v5. The standard prefers it over v3 for new work. Pick UUID v3 only to match IDs that an older system already made with MD5.