Monday, Mar 30, 2026 at 19:24
i admit i just grabbed your gibberish and dumped it into copilot and it spat this out
What you’re running into is how map “tiles” and zoom levels work, and how that differs from simply looking at the same area in Google Maps.
I’ll break it down plainly, because this trips a lot of people up.
1. What a “tile” actually is (and why credits drop fast)
Most mapping platforms (MapTiler, Mapbox, Nearmap exports, etc.) use a tile pyramid:
A tile is a fixed-size image (usually 256×256 px or 512×512 px)
Tiles are requested by zoom level
Credits are consumed per tile, not per screen view
So even if you think you’re looking at a small area:
Your screen may be pulling dozens or hundreds of tiles
Panning or slightly zooming forces new tile requests
Each request burns credits immediately
?? A 200-credit drop is very normal from:
One zoom in/out
One pan
Or briefly loading a higher zoom level
2. Why Google Maps looks “free” (but isn’t comparable)
When you view imagery in Google Maps (the website or app):
You are not consuming tiles directly
Google does not expose tile counts or credits to end users
Imagery is:
Heavily cached
Adaptive to your device
Often downsampled unless you zoom all the way in
So Google Maps can appear:
Sharper at first glance
Less “costly” to browse
But that’s because:
You’re viewing a consumer UI, not a metered API or export service.
3. Resolution vs Zoom (this is the key misunderstanding)
Zoom level ? resolution in the way most people expect.
Typical zoom levels (approximate ground resolution):
ZoomResolution (m / pixel)Notes16~2.4 m/pxSuburban overview17~1.2 m/pxBuildings clear18~0.6 m/pxRoof detail19~0.3 m/pxHigh detail20–21~0.15 m/pxOnly where imagery exists
Important:
If you request Zoom 19, the system must fetch 4× as many tiles as Zoom 18 for the same area.
So:
“Just zooming in a bit” can quadruple tile usage
Even if the imagery itself isn’t actually higher quality
4. Why your test likely cost ~200 credits
Common causes:
? You hit a higher zoom level than you realised
Mouse wheel zoom
Trackpad pinch
Auto-fit to screen at high DPI
? Retina / high-DPI screen
A 4K display can request 2×–4× tiles
Some platforms silently fetch 512px tiles
? The imagery didn’t improve, but tiles still loaded
Imagery resolution is fixed by source
Platform still loads higher-zoom tiles even if they’re upscaled
? Cached vs uncached tiles
First view costs credits
Subsequent
views may not (depends on provider)
5. Why Google Maps and paid tiles don’t “match”
Google Maps imagery:
Varies by location
Often blends multiple dates/sources
May look sharper because of post-processing
Paid tile
services:
Give you raw, consistent tiles
No UI smoothing
No free caching beyond your plan
So visually:
Google Maps can look “better”
But you can’t legally export or reuse that imagery
Tile platforms charge because they allow use, export, and analysis
6. Practical ways to avoid burning credits
If you’re testing again:
Lock your zoom level
Do not scroll-wheel zoom
Test at Zoom 17–18 first
Only go higher if detail truly improves
Limit viewport size
Smaller browser window = fewer tiles
Check tile size setting
256px vs 512px matters a lot
Use bounding boxes instead of free pan
One request instead of many
AnswerID:
649092