Code tool

JSON File Splitter

Split one UTF-8 JSON file (≤5 MB) by items per part (1–100,000), an exact number of balanced parts (1–100, including empty parts), or a UTF-8 byte cap (2–20,000,000). Compact serialized JSON bytes include keys, commas and brackets. Whole top-level values stay together; an oversized item rejects the task. At most 100 JSON parts, 20 MB combined JSON output, and a STORE ZIP ≤21 MB. Root arrays and objects are supported; integer keys follow JavaScript key order.

In-browser processingNo account requiredPrivacy details ↗

    Split one UTF-8 JSON file (≤5 MB) by items per part (1–100,000), an exact number of balanced parts (1–100, including empty parts), or a UTF-8 byte cap (2–20,000,000). Compact serialized JSON bytes include keys, commas and brackets. Whole top-level values stay together; an oversized item rejects the task. At most 100 JSON parts, 20 MB combined JSON output, and a STORE ZIP ≤21 MB. Root arrays and objects are supported; integer keys follow JavaScript key order.

    JSON is parsed and reserialized, so whitespace and number spelling change. Duplicate keys inside a file keep the last value. JavaScript floating-point rounding applies; non-finite values and unsafe integers are rejected. UTF-8 is required; an initial BOM is accepted. Maximum depth: 64 (root depth 0); maximum 100,000 value/container nodes across all input files and in the result. Exceeding a limit rejects the whole task and clears downloads.

    A QUICK WALKTHROUGH

    How to use this tool

    1. Choose files, check the displayed order and options, then run and download.

    Workflow

    Split one UTF-8 JSON file (≤5 MB) by items per part (1–100,000), an exact number of balanced parts (1–100, including empty parts), or a UTF-8 byte cap (2–20,000,000). Compact serialized JSON bytes include keys, commas and brackets. Whole top-level values stay together; an oversized item rejects the task. At most 100 JSON parts, 20 MB combined JSON output, and a STORE ZIP ≤21 MB. Root arrays and objects are supported; integer keys follow JavaScript key order.

    Local processing; files are not uploaded.

    JSON is parsed and reserialized, so whitespace and number spelling change. Duplicate keys inside a file keep the last value. JavaScript floating-point rounding applies; non-finite values and unsafe integers are rejected. UTF-8 is required; an initial BOM is accepted. Maximum depth: 64 (root depth 0); maximum 100,000 value/container nodes across all input files and in the result. Exceeding a limit rejects the whole task and clears downloads.

    GOOD TO KNOW

    Common questions

    Workflow

    Choose files, check the displayed order and options, then run and download.