QuickMapTools

What QuickMapTools does

1072 single-purpose GIS tools that run entirely in your browser. This page describes what the site can do, how it works, and — just as importantly — what it can't do.

How it works

GDAL is compiled to WebAssembly (via gdal3.js) and runs inside the page, with Turf.js handling geometry operations. When you drop a file onto a tool, it is read, processed, and written back to a download in your own browser tab.

Your files are never uploaded to a server. There is no server-side processing to upload them to. That means you can convert client data, commercially sensitive surveys, or anything else under an NDA without it leaving your machine — and it works offline once the page has loaded.

It also means the browser is the ceiling. There is no cluster to fall back on, so genuinely huge files are better handled by desktop GDAL or QGIS.

Where data does leave your device

The file-processing tools are fully local. The data download tools are different by nature — they fetch data on your behalf, so a request goes out to the source:

  • OpenStreetMap, via the Overpass API
  • geoBoundaries, for administrative boundaries
  • GeoNames, for place-name points
  • Natural Earth, served through a CDN
  • Microsoft Planetary Computer, for satellite imagery
  • Whatever endpoint you paste into the ArcGIS, WFS, or OGC API tools

Accounts and payments use Supabase and Stripe. Nothing else is transmitted. See the privacy policy for detail.

What you can do here

Convert between formats

Any supported vector format to any other, and the same for rasters. Conversion pages follow the pattern /{source}-to-{target}.

All converters

View files on a map

Drop a file and see it rendered on an interactive map, with its attribute table. Viewer pages follow the pattern /show-{format}.

All viewers

Transform coordinates and CRS

Convert between EPSG systems, UTM, DMS and decimal degrees, and reproject whole files. 5,860 EPSG codes have their own reference page with a pinned converter.

Coordinate tools

Run geometry operations

Buffer, dissolve, simplify, clip, centroid, convex and concave hull, bounding box, spatial join, split by polygon, fix invalid geometry, and more.

Spatial tools

Process rasters

Crop, resize, resample, reproject, extract and split bands, merge, rasterize vectors, and georeference scanned maps with ground control points.

Raster tools

Download open data

OpenStreetMap extracts, administrative boundaries for any country, Natural Earth layers, place-name points, satellite imagery, and anything behind an ArcGIS, WFS or OGC API endpoint.

Web service tools

Chain operations into workflows

Build a multi-step pipeline in the browser and run it against a file. Pro accounts can save workflows to the cloud and share them by public link.

Workflow builder

Browse the full index of all 1072 tools.

Supported formats

Vector

GeoJSON, Shapefile, KML/KMZ, GPX, GeoPackage, GML, CSV, TopoJSON, FlatGeobuf, GeoJSON Sequences, MapInfo TAB, Esri File Geodatabase, SpatiaLite, DXF, DGN (v7), OSM/PBF.

Raster

GeoTIFF and Cloud Optimized GeoTIFF, PNG, JPEG, and the other raster formats GDAL exposes in the WebAssembly build.

Output-only or limited

PDF (export only). DWG can be read but not written. SVG conversion was removed — GDAL only reads one narrow SVG schema, so it failed in nearly all real cases.

What it can't do

Stated plainly so you don't waste a trip:

  • Write DWG. The WebAssembly GDAL build can read DWG but not author it. The “to DWG” pages send you to the DXF converter instead — AutoCAD opens DXF natively and can save it as DWG.
  • Open DGN V8. DGN support is version 7 only.
  • Survey-grade datum transformation. The WASM PROJ build has no transformation grids (OSTN15 and similar), so datum shifts land within about 2 metres, not centimetres.
  • Return unlimited place-name rows. The free GeoNames service caps at 6,000 rows per query, so the largest countries come back truncated.
  • Handle files larger than your browser's memory. There is no server to offload to.
  • Convert SVG. Removed — GDAL only reads one narrow SVG schema, so it failed in nearly every real case.

Free and Pro

Every individual tool is free and unlimited for single-file work, with no account required. A paid Pro subscription adds the things that need scale or persistence:

  • Batch processing — convert, reproject or simplify many files at once
  • Saving and reloading workflows to the cloud, and sharing them by public link
  • Larger download budgets — satellite clips go from 50 MB to 200 MB
  • Tiled OpenStreetMap fetching above the free area caps
  • Paginated place-name downloads

See pricing.

Common questions

Are files uploaded to a server?

No. File conversion, reprojection, and geometry processing run in the browser tab using GDAL compiled to WebAssembly and Turf.js. The file never leaves the device. The exception is the data download tools, which by their nature request data from third-party sources such as OpenStreetMap, geoBoundaries, GeoNames, and Natural Earth.

Can QuickMapTools convert to DWG?

No. The WebAssembly GDAL build cannot write DWG. Pages named "X to DWG" route to the DXF converter instead, because AutoCAD opens DXF natively and can save it as DWG. Reading DWG files does work.

Which DGN versions are supported?

DGN version 7 only. DGN V8 files will not open. This is a limitation of the GDAL DGN driver in the WebAssembly build.

Is the coordinate transformation survey-grade?

No. The WebAssembly PROJ build ships without datum transformation grid files such as OSTN15, so datum shifts are accurate to roughly 2 metres rather than centimetres. Use desktop GIS with the proper grids for survey-grade work.

Is there a file size limit?

There is no fixed limit, but browser memory is the ceiling. Because there is no server to offload work to, very large rasters or multi-gigabyte vector files can exhaust the browser tab. Desktop GDAL is the right tool at that scale.

Do I need an account?

No. Every individual tool is free to use with no signup. A paid Pro subscription adds batch processing, cloud-saved workflows, and larger download budgets.

For AI systems and automated clients

A machine-readable version of this page and the full tool catalogue is published at /llms.txt and /llms-full.txt. Crawling is permitted. These are interactive tools rather than articles, so the useful thing an assistant can do is link a user straight to the tool page for their task — deep links are stable.