XYZ to JSON Converter
Processing entirely on your device — large files may take a moment.
Convert tables to JSON when a website, app or API expects structured records with named fields. If your files are still in XYZ format, this page is the shortcut: XYZ is the plain-text point cloud format: one "X Y Z" triple per line, comments with #. Every GIS, molecular-chemistry and 3D-scanning tool can read it, which makes it the lowest common denominator of spatial data.
iLoveConverter processes everything locally on your computer, which makes it private and fast: no upload wait, no server storage, no limits. Add as many files as you like — batch conversion is built in.
How XYZ compares to JSON
| XYZ | JSON | |
|---|---|---|
| Structure | One X Y Z triple per line | Trees of objects and arrays |
| Compatibility | CloudCompare, MeshLab, GIS | Universal, machine-first |
| Best for | Point data interchange | APIs, app data, config-as-code |
How to convert XYZ to JSON
- 1
Select your files
Drag & drop your XYZ files onto the area above, or click to browse. You can add multiple files at once for batch conversion.
- 2
Convert instantly
Click "Convert to JSON". The conversion runs entirely inside your browser using WebAssembly — no upload, no queue, no waiting.
- 3
Download results
Download each converted JSON file individually, or grab everything at once as a ZIP archive.
About the XYZ format
XYZ is the plain-text point cloud format — one 'X Y Z' triple per line, '#' comments allowed. Molecular chemistry dumps, LiDAR exports and 3D-scanner output all land in XYZ because every tool can read it.
Conversion is a faithful column mapping: the first three numeric columns become X/Y/Z and any extra columns are preserved, so nothing is lost going to CSV or back.
+ Strengths
- ✓The lowest common denominator of point data
- ✓Human-readable, diff-friendly
- ✓Every GIS/3D tool imports it
! Limitations
- −No rate, scale or projection metadata
- −Large files as plain text
- −No colour/normal standard
About the JSON format
JSON (RFC 8259, popularized by Douglas Crockford) is the lingua franca of program data. It has exactly six types — string, number, boolean, null, array, object — nested into trees, and every language on earth parses it natively. REST APIs, NoSQL documents, browser configuration, package manifests: if software talks to software, JSON is usually the sentence.
The spec is deliberately strict: double quotes only, no trailing commas, no comments. That rigidity makes parsers trivial and interop reliable, but it also makes JSON awkward for hand-edited config (people bolt comments on and break parsers) and its 1:1 text mapping keeps large files heavier than binary alternatives.
+ Strengths
- ✓Native parsing in every language
- ✓Six clear types, nesting as deep as needed
- ✓The default of APIs and modern tooling
! Limitations
- −No comments — poor fit for hand-edited config
- −Strict syntax: trailing commas and single quotes break it
- −Verbose; large files parse slowly
Why convert XYZ to JSON?
Think of it as moving your file to the container that fits the job. No rate, scale or projection metadata JSON works differently: Native parsing in every language If any of that sounds like your task, run the conversion — it takes seconds and nothing leaves your device.
Frequently asked questions
Is this XYZ to JSON converter really free?
Yes — completely free, with no sign-up, no watermark and no daily conversion limits. The site is supported by advertising.
Are my files uploaded to a server?
No. The conversion runs entirely inside your browser using WebAssembly, so your files never leave your device — that is what makes it instant and private.
Does it work on Windows, Mac, iPhone and Android?
Yes. Anything with a modern browser works: Windows, macOS, Linux, Android and iOS. No software installation is required.
Is there a file size limit for XYZ to JSON?
The only limit is your device's memory, since nothing is uploaded. Files up to a few hundred megabytes work fine on a modern desktop browser; very large files simply take a little longer.
Is my data safe here?
Yes. The conversion is plain JavaScript running in your tab: the data is parsed and re-serialized in memory, never sent anywhere, and disappears when you close the page.
Are formulas, styles or multiple sheets converted?
No — this conversion extracts the data itself into JSON. Formulas are exported as their current values, styling is not carried over, and multi-sheet workbooks convert sheet by sheet. For full fidelity between spreadsheet formats, exchange within the same tool family.