GeoConvert Overview
GeoConvert is a cloud service that converts between GeoJSON, Shapefile, and about 17 other vector GIS formats (GeoPackage, KML, GPX, XLSX, GeoParquet, and more) for GIS workflows.
What GeoConvert Does
- Converts GeoJSON or Shapefile input to any supported target format, with configurable target EPSG
- Converts multiple files in a single batch request, with the output format selectable per file
- Runs a pre-flight data-loss report before a lossy GeoJSON→Shapefile conversion
- Tracks conversions as jobs with status and downloadable output
- Supports web UI usage and API automation
Ways to Use GeoConvert
Web UI
Use the GeoConvert page in the CADshift web app to upload files, run conversions, and download results.
API
Automate conversions through the GeoConvert API. See the GeoConvert API Reference for the full endpoint list, request and response details.
All API calls require the X-API-Key header.
API keys are available on every plan, including the free tier; free-tier API calls use the same free conversions as the web UI. Create keys on the GeoConvert subscriptions page. In an organization only an org admin creates keys, and members use the admin’s keys.
Typical Conversion Flow
API (X-API-Key)
- Call
POST /api/geoconvert/convert/filewith the input file and an optionaloutputFormat(multipart/form-data) — orPOST /api/geoconvert/convert/batchto convert several files, each with its ownoutputFormatsentry, in one request. - Poll
GET /api/geoconvert/convert/jobs/{jobId}/statusfor status. - Download the output from
downloadUrlwhile it is valid.
Plans, Limits and Retention
GeoConvert is sold as monthly plans. Each plan is a monthly allowance of input data and conversions, a cap on the size of a single file, and a retention period for downloads:
| Plan | Price (USD, before tax) | Data a month | Largest file | Conversions a month | Downloads kept |
|---|---|---|---|---|---|
| Free | 0 | 50 MB | 5 MB | 10 | 4 hours |
| Personal | 9 / month or 90 / year | 1 GB | 25 MB | 500 | 2 days |
| Team (organisation) | 49 / month or 490 / year | 10 GB | 100 MB | 5,000 | 2 days |
| Business (organisation) | 199 / month or 1,990 / year | 50 GB | 100 MB | 25,000 | 2 days |
- Limits are hard: a conversion that would exceed the plan’s per-file cap, data allowance or conversion allowance is refused with
needsUpgrade: trueandlimitnaming the limit (fileSize,data,conversions). There are no overage charges; the allowance resets every month on every plan, annual billing included. - Every file counts separately, including each file of a batch or ZIP request, and its size counts toward the data allowance. A conversion is counted only once its output is stored; if the allowance ran out in the meantime the job fails and nothing is delivered.
- The upload ceiling is 100 MB per file on any plan; batch requests take up to 20 files and 200 MB total.
- Download links and stored outputs last the plan’s retention, counted from the conversion; after that the link stops working and the output is deleted.
- Accounts still spending prepaid credit bought before the plans keep spending it per file at the old rates (
newWalletBalanceCentsin the responses); when it reaches zero they are on the Free plan.
If you lose the response that carried a job’s downloadUrl, list your recent jobs with GET /api/geoconvert/convert/jobs; every completed job whose link is still valid comes back with a fresh URL.
Use GET /api/geoconvert/pricing/tiers to read the current plans, and GET /api/geoconvert/account/usage to read the plan in force and what is left of this month’s allowance.
Storage Regions
Business plans choose the storage region for their outputs on the GeoConvert account page (an organisation’s admin chooses for every member); every other plan uses the site default.
Organization Access
A Team or Business plan belongs to an organisation and its allowance is shared by every member. Admins buy and manage the plan, invite members by email (Microsoft work accounts from a consented Entra ID tenant join automatically), create the API keys members use, and can restrict access to one Azure AD group. API keys stay per user; the usage counts to the organisation.
Related Docs
- Next
- API Reference