5 KB GeoJSON sample

A GeoJSON file of exactly 5,120 bytes. It is a valid GeoJSON file, generated by this site. Compare its checksum and test it with the parser used by your application. Use it wherever you need a 5 KB sample, test or dummy GeoJSON file.

Download

sample-geojson-5kb.geojson

5 KB5,120 bytes

Download 5 KB GeoJSON

Created in your browser in a few seconds, then checked against the SHA-256 checksum. The file is not uploaded anywhere. No sign-up.

Type
application/geo+json
SHA-256
c04c13fdcee9deaeaca4adc241354e053d4989601991f206397be931d3fbb880
Delivery
Created in your browser from static generator assets (how it works).

What is in this file

A FeatureCollection of 25 features: 24 points and 2 line strings with longitude-latitude coordinates (WGS 84) and properties. A "padding" member, which GeoJSON readers ignore, brings the file to the exact size.

Features25
Geometry typesPoint, LineString
Coordinate referenceWGS 84 (RFC 7946)
EncodingUTF-8 (ASCII characters only)

How the file begins

The opening lines of sample-geojson-5kb.geojson, exactly as they appear in the file.

00000000  7b 0a 20 20 22 74 79 70  65 22 3a 20 22 46 65 61 |{.  "type": "Fea|
00000010  74 75 72 65 43 6f 6c 6c  65 63 74 69 6f 6e 22 2c |tureCollection",|
00000020  0a 20 20 22 6e 61 6d 65  22 3a 20 22 53 61 6d 70 |.  "name": "Samp|
00000030  6c 65 20 47 65 6f 4a 53  4f 4e 20 66 69 6c 65 20 |le GeoJSON file |

Preview

Shows the file contents.

Where 5 KB matters

A 5,120-byte file: larger than a cookie, smaller than a typical HTTP header limit. These are the default limits a file of this size is useful for testing:

SystemLimitNote
Browser cookies4,096 bytes per cookie5 KB does not fit in one cookie.
Vite asset inlining4 KB by default (assetsInlineLimit)A 5 KB asset is emitted as a separate file rather than inlined as base64.
nginx and Apache request headers8 KB per header line by default5 KB fits; the 10 KB sample does not.

All 5 KB sample files

Use this file for

  • Smoke tests in CI that must run in milliseconds
  • Testing map layers and spatial queries
  • Checking coordinate-order handling

Testing notes for GeoJSON

  • Swapped latitude and longitude put points in the wrong hemisphere or the ocean. Test with locations you can recognise.
  • Polygon rings must be closed, with the first and last positions identical.

GeoJSON format reference

Technical details

File namesample-geojson-5kb.geojson
FormatGeoJSON (GeoJSON)
Extension.geojson
MIME typeapplication/geo+json
Size5,120 bytes (5 KB)
KindText
SHA-256c04c13fdcee9deaeaca4adc241354e053d4989601991f206397be931d3fbb880
Created2026-10-23
ValidationSee the listed size and SHA-256. Small downloads are checked in the browser; verify streamed downloads manually. A hash match does not prove parser compatibility.
PreviewAvailable on this page
SourceGenerated in your browser by this site's generator; not copied from elsewhere
LicenceFree to use, modify and redistribute (terms)
CategoryGIS

Check the stated structure and checksum against your application requirements. As with any download, scan the file with your own security tools before opening it. How files are made and checked

Verify your copy

This file is created in your browser, so it has no direct URL for curl or wget. The generator is designed to produce reproducible bytes. After saving, compare the checksum with the SHA-256 value above.

sha256sum sample-geojson-5kb.geojson     # Linux
shasum -a 256 sample-geojson-5kb.geojson # macOS

On Windows, run Get-FileHash sample-geojson-5kb.geojson -Algorithm SHA256 in PowerShell. For scripts and pipelines, save the file once and keep your own copy.

Related files

Questions about this file

Is this file exactly 5 KB?
Yes. It is 5,120 bytes, which is 5 KB in the binary units that operating systems and server limits use (1 KB = 5,120 bytes).
What is inside the 5 KB GeoJSON file?
A FeatureCollection of 25 features: 24 points and 2 line strings with longitude-latitude coordinates (WGS 84) and properties. A "padding" member, which GeoJSON readers ignore, brings the file to the exact size.
Where are the sample features located?
Near sixteen real cities on six continents, with small random offsets, so the result is easy to check on a map.