What scale looks like

These are honest comparisons, not rounded up for effect. The source numbers are from the system I run today: a 383 GB database holding about 224 million rows across 86 case, corpus, and law schemas, with 14,003,303 searchable text chunks in the unified evidence search alone. A chunk is about 1,000 characters, roughly a third of a printed page.

Every comparison below starts from that one number, 14,003,303 chunks, and shows the arithmetic.

1. Pages

14,003,303 chunks divided by 3 chunks per page is about 4,667,768 pages. That is the working figure behind every comparison that follows.

2. Books

At 300 pages to a book, 4,667,768 pages is about 15,559 books.

3. Bankers boxes

A standard bankers box holds about 2,500 pages. 4,667,768 pages divided by 2,500 is about 1,867 bankers boxes, more than a semi-trailer could carry stacked as paper.

4. Reading time

At 400 words per page, 4,667,768 pages is about 1,867,107,200 words. At a working reading speed of 250 words a minute, that is 7,468,429 minutes, or 124,474 hours.

• Read around the clock, no breaks: 124,474 hours divided by 24 is about 14.2 years, nonstop.
• Read as a full-time job, 40 hours a week, 52 weeks a year, no vacation: 124,474 hours divided by 2,080 hours a year is nearly 60 years, a full working career, to read this file once.

5. Shelf feet

A 300-page book runs about 25 mm thick on the spine. 15,559 books times 25 mm is 388,980 mm, or about 389 meters, which converts to about 1,276 linear feet of bookshelf. A football field is 300 feet end zone to end zone; that is more than four football fields of shelving, side by side.

6. Height, stacked

A sheet of paper is about 0.1 mm thick. 4,667,768 pages times 0.1 mm is 466,777 mm, or about 467 meters, stacked as one column.

The Empire State Building is 381 meters to the roof and 443 meters to the tip of its antenna. A stack of every page in the database, laid one on top of the other, is taller than the Empire State Building, including the antenna, by about 24 meters.

7. Reviewing every row by hand

Beyond the text chunks, the database holds about 224 million rows total across every table: parties, events, dates, financial line items, docket entries. Reviewing one row a second, around the clock, is 224,000,000 seconds, or about 2,593 days, or about 7.1 years, nonstop, just to look at each row once, before reading what is in it.

Other numbers in the same system

• About 10.7 million court-opinion rows pulled from CourtListener, the free federal case-law archive.
• 1,281,591 chunks of Oregon circuit-court records alone.
• A guardianship-law authority pack of 712 documents and 46,198 chunks: full Oregon statute text, administrative rules, UTCR, and appellate opinions, all loaded beside the evidence and searchable together, the Level 3 build applied to one practice area.
• One evidence folder in the system is Bates-stamped from page 00001 to page 16,716, a single case file bigger than most firms' entire physical archive.

What this means for your matter

Your file will not be this large. The point of these numbers is what the search does at scale: none of the comparisons above is something a person reads. It is something a database answers in seconds, cited to the page, whether the file is 500 pages or 14 million chunks.