Free map maker. Your files never leave your device.
Put a spreadsheet or a map file on a map, color it by a value, measure, and save a picture or a file. No account, nothing uploaded. This map shows borders, not streets.
Loading the map maker. It needs JavaScript and runs only in this browser.
Your files stay on your device. The map is made in this browser. Nothing you open is uploaded, we cannot see it, there is no account, and it is free. Nothing is kept after you close the page either, so save a project file if you want to come back to your work.
What it does: open a spreadsheet saved as CSV or TSV with latitude and longitude columns, or with a U.S. state column (name, two-letter code or FIPS number) or a five-digit county FIPS column and a number to shade by. It also opens GeoJSON, KML and KMZ, GPX and zipped shapefiles. Then color by a column, add labels, click anything to see and edit its details, sort and filter the table, measure, count points inside shapes, draw your own points, lines and shapes, and save it as GeoJSON, CSV, KML, GPX, a picture, a print layout or a project file.
How we measure: distances follow the shortest path over the earth, on the same model of the earth GPS uses (the WGS 84 ellipsoid), worked out with the standard step-by-step formula for it, which agrees with the exact answer to well under a millimeter. For two points almost exactly opposite each other on the globe it can fail to settle; then we use a round earth instead, which can be off by up to about half a percent, and we say so next to the result. Areas are worked out on the same ellipsoid. Each edge of a shape is taken as a straight line in latitude and longitude, which is what map files assume, and the map draws it that way; we follow each edge in small steps, and in our checks against two independent calculations the area came out within a hundred-thousandth of a percent of the exact area of that outline, thin slivers right next to the North or South Pole included. The result can only be as good as the outline: the built-in borders are simplified, so the area of a state measured from them is close, not official. A shape that goes around the North or South Pole is not measured. Inside tests (which points are in which shape) treat edges the same way, also for a shape that goes all the way around a pole, like Antarctica, and a point exactly on a border counts for every shape it touches.
- Streets. This map shows borders, not streets: countries, U.S. states and U.S. counties.
- Turning addresses into points. Your file needs latitude and longitude, or a U.S. state or county code.
- Other projections. A shapefile or GeoJSON must be in plain latitude and longitude in degrees from Greenwich (WGS 84 or NAD 83) or in Web Mercator; for anything else it says so and loads nothing. A shapefile with no .prj file opens only after you tell it the coordinates are latitude and longitude. Free desktop mapping programs can convert a file first.
- Buffers around lines and shapes, and combining shapes.
- Spreadsheet workbooks. Save the sheet as CSV first.
- Very large zip files. The files the tool reads inside a zip (the .shp, .dbf, .prj, .cpg or .kml) may unpack to at most 200 MB together; a zip whose files need more is refused. A KML, GPX or GeoJSON file may nest its parts at most 1,000 levels deep.
- Simplifying keeps every corner it drops within the tolerance, but at large tolerances an outline can come out crossing itself, and two shapes that share a border are simplified one at a time, so their shared border can pull apart by up to twice the tolerance.
- Longitudes past 180. A file must write longitudes between -180 and 180; one that writes a place past the 180th meridian as 181 degrees or more is refused, not guessed at. Shapes that cross the 180th meridian the usual way (from 179 to -179), like Alaska's western islands, are drawn in one piece and measured correctly.
Numbers: a dot is the decimal mark. A number written with a comma, like "12,5" or "1,234", stops the file from loading with a note saying which row; we never guess what it meant.
Where the borders come from: countries from Natural Earth (version 4.1.0, public domain), and U.S. states and counties from the U.S. Census Bureau's cartographic boundary files, 2017 edition (public domain), as packaged in TopoJSON (license for the world packaging, for the U.S. packaging). They are served from this site. County codes are the 2017 ones. The samples are made from these borders by this tool (county centers and a count of counties per state) or made up (the hike), so they hold no outside statistics. We also have a free photo editor, a free CRM and a free invoice maker.
Need maps or location data worked into your reporting?
We build dashboards and reports that put your sales, territories and customers on a map, with clean data behind them.