GUID Forge: Bulk UUID / GUID / ID Generator (Apify Actor)

Generate UUIDs, GUIDs, and custom IDs in bulk on Apify. This actor is built for fast, reliable identifier generation for databases, APIs, ETL pipelines, testing, and automation workflows.

Why Use This Actor

• Generate up to 5,000,000 IDs in one run.
• Supports UUID v1, UUID v4, UUID v5, alphanumeric IDs, and sequential IDs.
• Add optional prefix and suffix to every identifier.
• Output is clean JSON in the default Apify dataset: { "guid": "..." }.
• UUID v5 supports deterministic name templating for repeatable IDs.

Supported Types

• v1 / uuidv1: time-based UUIDs
• v4 / uuidv4: random UUIDs (default)
• v5 / uuidv5: namespace + name-based deterministic UUIDs
• alphanumeric: random IDs from a custom charset
• sequential: incrementing numeric IDs with optional timestamp prefix

Quick Start (Apify Console)

1. Open the actor and click Start.
2. Pick your type (for example v4, v5, alphanumeric, or sequential).
3. Set count.
4. Optionally set prefix / suffix and type-specific fields.
5. Run the actor and open the Dataset tab to download results.

Input Reference

• count (integer): number of IDs to generate. Min 1, max 5000000, default 5.
• type (string): v1, v4, v5, alphanumeric, sequential. Default v4.
• prefix (string): optional text prepended to every ID.
• suffix (string): optional text appended to every ID.
• validateUnique (boolean): in-memory duplicate validation. Default false, max supported 1000000 items when enabled.
• batchSize (integer): dataset push chunk size. Min 1, max 50000, default 5000.

UUID v5 fields (type: "v5")

• uuidV5Name (string): base name input. If omitted, default is guid-forge.
• uuidV5Namespace (string): DNS, URL, or a UUID namespace string. If omitted or invalid, default is DNS.
• uuidV5NameTemplate (string, optional): template tokens:
  • {{name}}
  • {{index}} or {{n}} (1-based)
  • {{index0}} (0-based)

Alphanumeric fields (type: "alphanumeric")

• alphanumericLength (integer): min 1, max 10000, default 16.
• alphanumericCharset (string): allowed characters. Default base62 charset.

Sequential fields (type: "sequential")

• sequentialStart (integer): default 1.
• sequentialStep (integer): default 1, cannot be 0.
• sequentialPadding (integer): min 0, max 50, default 6.
• sequentialTimestampPrefix (boolean): default true.
• sequentialTimestampUnit (string): ms or s, default ms.
• sequentialDelimiter (string): default -.

Example Inputs

1) UUID v4 (random GUIDs)

{
  "count": 1000,
  "type": "v4"
}

2) UUID v5 (deterministic)

{
  "count": 3,
  "type": "v5",
  "uuidV5Name": "customer",
  "uuidV5Namespace": "DNS",
  "uuidV5NameTemplate": "{{name}}-{{index}}"
}

3) Alphanumeric IDs with prefix

{
  "count": 10,
  "type": "alphanumeric",
  "alphanumericLength": 12,
  "prefix": "ORD-"
}

4) Sequential IDs for order numbers

{
  "count": 5,
  "type": "sequential",
  "sequentialStart": 1000,
  "sequentialStep": 1,
  "sequentialPadding": 8,
  "sequentialTimestampPrefix": false,
  "prefix": "INV-"
}

Output Format

Each dataset item has this shape:

{
  "guid": "a17e8844-f7e1-4bd1-913c-f68bb4a1ad4b"
}

Performance and Reliability Notes

• Use larger batchSize values for better throughput.
• Keep validateUnique disabled for very large runs to reduce memory usage.
• Sequential generation enforces JavaScript safe-integer bounds to prevent precision errors.
• UUID v5 runs continue even if uuidV5Name / uuidV5Namespace are missing; safe defaults are applied automatically.

Common Use Cases

• Bulk primary keys for database seeding
• Stable deterministic IDs for ETL joins (UUID v5)
• Order, invoice, or ticket ID generation
• Test data generation for QA and CI pipelines
• API tokens or internal reference code generation

Legacy Compatibility

The actor still accepts legacy aliases:

• guidType as alias for type
• name as alias for uuidV5Name
• namespace as alias for uuidV5Namespace