Handling Large JSON Files in Excel: The Performance Guide

Converting a small JSON snippet with 10 records is trivial. But what happens when you need to process a 50MB database dump or a 100,000-row transactional ledger from Stripe or Firebase?

In most online converter tools, opening a 20MB JSON file produces an immediate browser lockup, followed by the dreaded "Page Unresponsive" dialog. Let's explore the mechanics of browser memory, thread contention, and how modern Web Workers solve large-scale data transformation.

Why Browser Main Threads Lock Up

JavaScript in the browser runs on a single event-loop thread. That same thread is responsible for handling user mouse clicks, rendering typography, evaluating CSS styles, and painting frames at 60 FPS.

When you run JSON.parse() on a 50MB string, followed by recursive object traversal across 100,000 objects, that single thread is monopolized for several seconds. During that time, the user cannot scroll or click, and the operating system flags the browser tab as frozen.

The Solution: Off-Thread Web Workers

Web Workers allow developers to spin up background threads that run concurrently on separate CPU cores:

// Main thread stays responsive at 60 FPS
const worker = new Worker('/workers/converter.worker.js');
worker.postMessage({ action: 'PARSE_LARGE_DATASET', rawText });

worker.onmessage = (e) => {
  // Receives compiled Excel binary without blocking UI
  triggerDownload(e.data.bytes);
};
      

Managing Memory Allocation and Garbage Collection

When processing 100,000 rows, memory efficiency is critical:

• Avoid Deep Cloning: Directly mutate or build flat row buffers instead of duplicating large intermediary object trees.
• Sample Previews: Render only the first 25 to 50 rows in the DOM preview table. Injecting 100,000 DOM elements into a web page creates massive memory bloat.
• ArrayBuffer Transfer: When passing the compiled XLSX binary back from the worker to the main thread, transfer ownership of the underlying ArrayBuffer to avoid costly memory copying.