Why JSON Number Precision Breaks Large IDs
Debug large numeric identifiers, cents, timestamps and database ids that change value when parsed as JavaScript numbers.
Quick Answer
JavaScript numbers cannot safely represent every large integer. JSON payloads that send large ids, account numbers, nanosecond timestamps or high-precision amounts as numbers can lose precision in the browser. Send identifiers as strings when exact value matters.
Example Scenario
An API returns a large order id as a JSON number. The backend logs 9007199254740993, but the browser displays 9007199254740992. The JSON is valid and the request succeeded, yet the identifier changed during parsing.
Step-by-Step Explanation
- Check whether the value exceeds Number.MAX_SAFE_INTEGER.
- Identify ids and exact decimal values that must not be rounded.
- Compare raw JSON text with parsed JavaScript values.
- Send large identifiers as strings.
- Avoid arithmetic on exact identifiers.
- Add tests around max safe integer boundaries.
Start by Naming the Contract That Broke
JSON number precision breaks large ids when exact integers are parsed into JavaScript Number values. Debugging is slower when every symptom is treated as a generic API failure. Name the contract first: request shape, response shape, retry behavior, file type, time zone, numeric precision, logging policy or delivery semantics. Once the contract is named, each observation has a place to belong.
The most useful first signal is usually a parsed id differs from the raw JSON text. It tells you which boundary produced the failure and prevents the team from rewriting unrelated client code. Keep the original request, response or log line available while you investigate.
A good working note should say what was expected, what actually happened and which layer observed it. That note is more valuable than a screenshot of a stack trace because it can be compared with documentation, tests and production logs.
If the issue is intermittent, keep one failing sample and one passing sample from the same release window. The passing sample prevents overfitting the fix to one user, while the failing sample keeps the investigation grounded in evidence instead of guesses about the system.
Separate Symptoms from Evidence
The visible symptom may be values near or above Number.MAX_SAFE_INTEGER, but the evidence should be more precise. Capture the raw response text before JSON parsing, then compare it with a successful case from the same environment. Environment, user role and feature flag differences can otherwise look like code regressions.
Avoid starting with broad fixes. First check the parsed JavaScript value and safe-integer check. If that detail differs from the healthy request, you have a concrete lead. If it matches, move to the next layer instead of guessing.
When multiple teams are involved, preserve the raw evidence in a safe form. Redact secrets, but keep field names, status codes, headers, timestamps and request ids. Sanitized evidence still lets another team reproduce the reasoning.
Look for Boundary Translation Errors
Many production bugs happen when data crosses a boundary and changes meaning. A browser form, generated client, proxy, queue worker, database mapper or logging pipeline can transform the value before the final system sees it.
For this issue, inspect whether the field is an identifier, amount or timestamp. That is where small differences usually become visible. A value may still look reasonable to a human while failing the receiver's stricter expectation.
Use comparison tools when the payload is large. Diff the failing sample against a known-good sample, then reduce it to the smallest input that still fails. A minimal failing sample turns a vague incident into a contract discussion.
Boundary errors also need ownership clarity. Decide which component is allowed to transform the value and which component must reject it. Without that decision, every layer may add a small compatibility patch, and the system becomes harder to reason about after the incident.
Choose a Fix That Matches the Failure Mode
The first safe fix is often serializing exact identifiers as strings. It addresses the observed boundary instead of hiding the symptom. If the problem is a contract mismatch, the fix should update the producer, consumer or documented contract deliberately.
The second fix to consider is using decimal or BigInt handling only at controlled boundaries. This is useful when old clients, partner integrations or delayed deployments mean two shapes must be accepted for a short time. Compatibility should be explicit and temporary where possible.
A third option is adding diagnostics for unsafe numeric fields. Use this when the system needs better operational visibility before making a behavioral change. Good diagnostics can prevent a small correction from becoming a larger regression.
Keep Production Diagnostics Safe
Diagnostics should explain the failure without exposing sensitive data. For this topic, useful logs include request id, status code, safe field paths, environment and a short reason code. They should not include tokens, full personal records or secret payloads.
If the failure reaches support, include raw value, parsed value and field purpose recorded together. That gives the next debugger a trail without requiring access to private customer data. It also helps separate one-off bad input from a systemic contract drift.
When adding logs, add deletion and retention awareness. Debug logs that are safe today can become risky if they accumulate raw payloads for months. Prefer structured fields over copied bodies.
A safe diagnostic should also be cheap to leave in place. If it requires developers to enable raw payload logging during every incident, the next emergency will recreate the same privacy and security risk. Prefer stable reason codes, counters and compact metadata that can remain active in production.
Prevention Checklist
Add a regression test for large id and high-precision amount examples. The test should fail when the boundary behavior changes unexpectedly. A small test around the contract is often more valuable than a broad snapshot that nobody reviews.
Review API schema review for integer format assumptions during release. Many bugs in this category appear during rolling deploys, integration updates or data migrations, not during a clean local run.
Document which numeric fields are safe for arithmetic and which are identifiers. The goal is not a long policy page; it is a short, accurate rule that future developers can apply while changing the same path.
After the fix, replay the original failing case and one known-good case. If both behave correctly, record the evidence in the incident or changelog. This closes the loop and keeps the next investigation from starting over.
Code Examples
console.log(Number.MAX_SAFE_INTEGER);
console.log(Number.isSafeInteger(payload.orderId));const text = '{"id":9007199254740993}';
console.log(text);
console.log(JSON.parse(text).id);const payload = { orderId: '9007199254740993' };
console.log(JSON.stringify(payload));Common Mistakes
- Sending database ids as JSON numbers by default.
- Assuming valid JSON preserves every integer exactly in JavaScript.
- Doing arithmetic on identifiers.
- Mixing cents, decimals and floating point values carelessly.
- Testing only small ids generated in development.
FAQ
What is the max safe integer?
JavaScript Number safely represents integers up to 9007199254740991.
Should ids be strings in JSON?
Large or externally meaningful identifiers should usually be strings.
Does JSON itself lose precision?
The text does not, but the parser target type may.
Can BigInt fix it?
BigInt can help in controlled code, but JSON does not parse BigInt natively.