How GeoJSON Cloud works

One short, indexable summary of the product: local browser processing, optional cloud projects, and what we intentionally do not claim.

Differentiator in one sentence: guest tools and the editor convert, validate, repair, and edit geospatial data in your browser; files are not uploaded for those local workflows. Cloud save, share links, auth, analytics, map tiles, and optional remote URL fetch are separate paths described below.

What you can do without an account

Convert KML, zipped Shapefile, CSV, WKT, TopoJSON, and GeoJSON using free tools and the editor.
Validate GeoJSON for common structural issues and repair fixable cases (root normalization, unclosed rings).
Edit features on an OpenStreetMap basemap, then download GeoJSON.
Batch multiple supported files into one FeatureCollection, or reproject with a known source CRS.

What stays local vs what leaves the browser

Local workflows parse files with client-side libraries (for example shpjs, togeojson, papaparse, proj4) and keep the FeatureCollection in memory or sessionStorage drafts. We do not claim that every network request is eliminated: basemap tiles, optional place search, product analytics, authentication, and saved projects use the network. Full detail: Privacy in practice.

When you create an account

Free accounts can save one cloud project, share a public map (with attribution), and get a monthly conversion allowance in the signed-in editor. Pro unlocks unlimited conversions, multi-format export, and more projects (file size stays at the same practical browser ceiling). See the formats & limits matrix and pricing.

Accuracy boundaries

Validation and repair cover common RFC 7946 structure problems—not full GIS topology. Read accuracy & edge cases before treating output as authoritative for cadastral or engineering work.

When another tool is better

For huge datasets, advanced topology, CAD, or heavy batch automation, prefer Mapshaper, desktop GIS, or specialized converters. We document that tradeoff on Compare tools.