IDs list to JSON array: fast conversion for configs
IDs show up everywhere: allowlists, blocklists, feature flags, internal product catalogs. Converting an ID list into JSON makes it easy to plug into code and config files.
Keep IDs as strings (usually)
IDs are identifiers, not numbers. Treat them as strings to preserve leading zeros and avoid accidental numeric formatting. A JSON array of strings is the safest default for configs.
Cleaning rules
- Trim whitespace and drop empty lines.
- Remove invisible separators (copied from spreadsheets) by re-pasting as plain text if needed.
- Optionally dedupe if your consumer expects uniqueness.
Where this is used
Common uses include feature gating, fraud filters, customer segmentation lists, and import/export pipelines. Converting locally avoids leaking internal identifiers.
Practical checklist (fast)
If you’re stuck, use this quick checklist to narrow the problem before you try “random fixes”. Start by validating the input format (syntax first), then confirm shape expectations (array vs object, headers vs rows). Convert a small sample, inspect the output, and only then export the full result.
- Validate: confirm the input is strict JSON/XML/CSV (no stray characters).
- Confirm shape: arrays vs objects; headers vs row lengths; repeated tags vs arrays.
- Test a sample: first 20–50 rows/items are enough to detect parsing issues.
- Export: copy/download the output and re-check it in the consumer (script/spreadsheet/API).
This workflow is privacy-first by design: All processing happens locally in your browser. Files are never uploaded.
Practical checklist (fast)
If you’re stuck, use this quick checklist to narrow the problem before you try “random fixes”. Start by validating the input format (syntax first), then confirm shape expectations (array vs object, headers vs rows). Convert a small sample, inspect the output, and only then export the full result.
- Validate: confirm the input is strict JSON/XML/CSV (no stray characters).
- Confirm shape: arrays vs objects; headers vs row lengths; repeated tags vs arrays.
- Test a sample: first 20–50 rows/items are enough to detect parsing issues.
- Export: copy/download the output and re-check it in the consumer (script/spreadsheet/API).
This workflow is privacy-first by design: All processing happens locally in your browser. Files are never uploaded.
FAQ
Can I store IDs as numbers? Only if you are 100% sure there are no leading zeros and the range fits safely.
Why avoid online tools for ID lists? IDs can be sensitive (customer IDs, internal keys). No-upload conversion keeps them on-device.
Trust note: All processing happens locally in your browser. Files are never uploaded.
Local verification snippet
Run a quick local check before export/convert:
const text = input.trim();
const value = JSON.parse(text);
console.log(Array.isArray(value) ? 'array' : typeof value);