UUID Generator

What does UUID Generator do?

UUID Generator creates universally unique identifiers (UUIDs) on demand, in bulk, directly on the Apify platform. It supports UUID versions 1, 3, 4, 5 and 7 following the RFC 9562 standard (the successor to RFC 4122), so you get spec-compliant identifiers every time — no custom scripts required.

Generate anywhere from a single UUID to one million in one run, then download them as JSON, CSV, Excel, or plain text, or pull them straight from the Apify API. Because it runs on Apify, you also get scheduling, integrations (Make, Zapier, n8n, webhooks), and programmatic access out of the box.

Why use UUID Generator?

• Stop reinventing UUID scripts. Reusable, hosted, and callable from any language via the API.
• Seed test data and databases. Generate primary keys, fixtures, and mock records for QA and load testing.
• Build microservices and distributed systems. Produce correlation IDs, request IDs, and entity keys at scale.
• Deterministic IDs when you need them. Versions 3 and 5 turn the same name into the same UUID every time — ideal for idempotent keys derived from domains, URLs, or other stable inputs.
• Sortable identifiers. Version 7 is time-ordered, so IDs sort chronologically — great for database indexes.

How to use UUID Generator

1. Click Try for free / Start.
2. Pick a UUID version (v4 random is the default and the most common choice).
3. Set the Count for how many you want (or, for v3/v5, fill in the Names list).
4. Optionally toggle Uppercase, Include hyphens, or the plain-text file output.
5. Click Save & Start. When the run finishes, open the Output tab to view, or Export the dataset as JSON/CSV/Excel.

Input

Configure the run from the Input tab or via the API. All fields are optional except the UUID version (which defaults to v4).

Field	Type	Description
version	string	UUID version: v1, v3, v4, v5, or v7. Default v4.
count	integer	How many UUIDs to generate (v1, v4, v7). Default 10, max 1,000,000.
macAddress	string	(v1 only) Optional MAC address to use as the node, e.g. 00:1a:2b:3c:4d:5e. Leave empty for a random node.
names	array	List of names to hash (required for v3 / v5). One UUID is produced per name.
namespaceType	string	Namespace for v3 / v5: dns, url, oid, x500, or custom. Default dns.
customNamespace	string	A custom namespace UUID, used when namespaceType is custom.
uppercase	boolean	Output uppercase letters. Default false.
hyphens	boolean	Include standard hyphens. Disable for compact 32-char hex. Default true.
savePlainText	boolean	Also save uuids.txt to the key-value store. Default true.

Example input

{
    "version": "v4",
    "count": 1000,
    "uppercase": false,
    "hyphens": true
}

Name-based (deterministic) example:

{
    "version": "v5",
    "namespaceType": "dns",
    "names": ["example.com", "apify.com"]
}

Output

Each generated UUID is stored as a separate item in the run's dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. When savePlainText is enabled, a newline-separated uuids.txt file is also written to the default key-value store.

Example output

[
    {
        "uuid": "4e7788c6-f084-4734-b65f-65bcbb3b968f",
        "version": "v4",
        "index": 0
    },
    {
        "uuid": "0cf1742f-7ffd-412b-896f-5498f6f41344",
        "version": "v4",
        "index": 1
    }
]

For name-based versions, each item also includes the source name and the namespace UUID used.

Data table

Field	Description
uuid	The generated UUID string (formatted per your options).
version	The UUID version that produced it (v1–v7).
index	Zero-based position within the run.
name	(v3/v5 only) The source name that was hashed.
namespace	(v3/v5 only) The namespace UUID used.

How much does it cost?

This Actor uses a simple pay-per-event price: a flat $0.01 per run, charged once each time you start the Actor — no matter whether you generate one UUID or a million. There is no per-result fee and no separate platform-usage charge to reason about, so the cost of a run is completely predictable. The Actor runs at the platform's minimum memory (128 MB) and finishes in seconds for typical batches.

Tips and advanced options

• Need sortable IDs for a database? Use v7 — identifiers are time-ordered and index-friendly.
• Need the same ID for the same input? Use v3 or v5 with a fixed namespace and names; the output is fully deterministic.
• Want compact IDs? Set hyphens to false for a 32-character hex string.
• Big batches: raise count (up to 1,000,000). Items are pushed in batches for efficiency.
• Automate it: schedule recurring runs or call the Actor from your own code with the Apify API/SDK to generate IDs on demand.

FAQ, disclaimers, and support

Which version should I pick? Use v4 (random) unless you have a specific need: v7 for sortable IDs, v1 for timestamp-based IDs, v3/v5 for deterministic name-based IDs.

Can I control the MAC address in v1 UUIDs? Yes. Set the macAddress input to embed a specific node, e.g. 00:1a:2b:3c:4d:5e. If you leave it empty, the Actor randomizes the node (and always randomizes the clock sequence), so v1 UUIDs never leak the host's real hardware address.

Are the UUIDs cryptographically random? Versions 4 and 7 use the system CSPRNG (Python's secrets), making them suitable for unpredictable identifiers. UUIDs are not a substitute for secret tokens, however.

Found a bug or have a feature request? Open an issue on the Actor's Issues tab. Custom solutions and tweaks are available on request.