no sign-up · no schema · zero config
Address in.
Correct geometry out.
pointkit turns a plain address into the exact literal your database expects, MySQL POINT, Postgres ST_GeomFromText, WKT, or GeoJSON. Axis order handled correctly, every time.
{{ heroDialectLabel }}
{{ heroResultText }}
Note: MySQL/MariaDB's default SRID 4326 axis order is lat/long, the reverse of standard WKT. pointkit swaps it automatically so this literal inserts correctly.
{{ heroErrorText }}
Buy more credits →
Same conversion, for a whole file.
Drop a CSV, tell us which column has the addresses, get your file back with one new geometry column added. No table, no schema, no column types to define.
Drag a .csv file here, or click to browse
One new column gets appended. Nothing else in your file changes. Max 50,000 rows / 25 MB per file.
{{ dropzoneErrorText }}
{{ fileName }} · {{ rowCount }} rows
Which column has the addresses?
| {{ h.label }} |
|---|
| {{ cell.value }} |
{{ batchErrorText }}
Buy more credits →
Pricing
1 credit = 1 address, whether it's a single lookup or a row in a CSV. No subscription, credits never expire.
Tier
Price
Limit
Free
$0
20 credits every day, no signup. Resets at UTC midnight.
Credits
from $0.006 / credit
Buy 1,000–100,000 at once, cheaper per credit the more you buy
FAQ
Is my data stored?
Individual addresses and their resulting coordinates are cached, so converting the same address again later doesn't trigger a repeat lookup or cost. Uploaded CSV files themselves aren't retained; they're processed in memory and discarded once your results are ready.
Which countries are supported?
Both US and international addresses are supported. Coverage and precision are strongest for the US; international addresses work too, though accuracy can vary more by region.
What does it cost?
Every visitor gets 20 free credits a day, no signup, resetting at UTC midnight. 1 credit converts 1 address, whether that's a single lookup or one row in a CSV. Past the daily free amount, buy credits in packs of 1,000 to 100,000 — priced at a single flat rate for the whole purchase, cheaper per credit the more you buy. Credits never expire and aren't a subscription.
What's the axis-order thing about?
WKT and GeoJSON expect coordinates as (longitude, latitude). MySQL/MariaDB's default spatial reference, SRID 4326, defines axis order as (latitude, longitude), the reverse. Get it backwards and your points silently land in the wrong place, with no error thrown. pointkit outputs the correct order for whichever dialect you pick.
Do I need a spatial column set up first?
No. pointkit just gives you the literal value; insert it into whatever column type you already have.
My CSV has more than one address-like column. What happens?
Pick the column with full addresses when prompted. pointkit converts one column per run.