When to use this tool
Check whether a geographic export is empty, spot obviously unexpected coordinate ranges, or create a tabular index of feature IDs and their original geometry. No map tiles or external geographic services are requested.
How to use it
- Select a .geojson FeatureCollection.
- Inspect counts, bounds and sample features.
- Choose CSV to export id, properties_json and geometry_json columns.
Supported scope and limits
32 MiB input; 50,000 features; 500,000 coordinates. GeometryCollection, reprojection, spatial joins and topology validation are not supported. Bounds are numeric inspection, not a guarantee of valid geography.
The default mode processes file bytes in your browser using Rust compiled to WebAssembly. Choose on-device only to prevent file uploads, or allow automatic edge and Kubernetes fallback. Cloud quotas apply. Outputs are separate downloads; originals are not overwritten. Prepared results can be saved in this browser’s Recent files for up to 24 hours, subject to a 100 MiB storage budget.
Questions about geographic files
Does conversion flatten all feature properties into columns?
No. It keeps properties and geometry as JSON text columns to avoid guessing a schema or losing nested structures.
Does it validate a coordinate reference system?
No. Review the source CRS and expected ranges in your geographic application.
Try an example and check the format
The sample button loads a small synthetic file. You can also download that sample and inspect it in another application. Read the GeoJSON RFC 7946 for format background. Source specifications describe the format; this page states which parts SizeMyFile implements.
Maintained by SizeMyFile · Updated November 15, 2026. Found an incorrect result? Contact info@seehash.com with a description and a non-sensitive example.
Related tools
Open the full file workspace · Compress images and PDFs · How file privacy works