About

We treat data as structure, not text.

OPENXMLJSON exists because general-purpose editors were never built for gigabytes.

Our approach

A different idea about big files.

Most tools load a file into an in-memory object graph, then choke when that graph is larger than your RAM. OPENXMLJSON does the opposite: the file is memory-mapped once and parsed into a flat index of fixed-size 24-byte node records that hold byte offsets — never copies of your data.

Tree navigation, display and search all work on those offsets, so memory tracks your working set, not the file size. Files too large to index eagerly fall back to on-demand indexing, so documents near or beyond available RAM still open. The result is a viewer that opens ~10 GB of JSON, XML or CSV in a blink — and lets you browse and query it like a database.

By the numbers

Engineered for scale.

A native Rust engine treats your data as structure, not text — so memory tracks your working set, not the file size.

~10 GB
Files open & search, no in-memory copy
24 B
Index per node — ~3 GB for 130M nodes
130M/s
Objects parsed per second
3
Editions: Essential, Premium, Narik

Stop waiting on progress bars.

Download OPENXMLJSON and open your biggest file in seconds.

Windows · macOS · Linux · Essential edition available