Question 1

How do I debug a WMS GetCapabilities response?

Accepted Answer

Paste your WMS endpoint into geodebug.io. It fetches GetCapabilities, parses the XML, lists available layers and CRSes, and renders any layer with one click — surfacing CORS, auth, and malformed-XML errors inline.

Question 2

Why won't my vector tiles load in MapLibre?

Accepted Answer

Common causes: missing CORS headers on the tile origin, a TileJSON minzoom/maxzoom mismatch, gzip not advertised in Content-Encoding, or the tiles being TMS-flipped y-axis. Paste the tile or TileJSON URL into geodebug.io to see headers, decoded MVT layer names, and zoom-level coverage.

Question 3

What is a PMTiles file and how do I preview one?

Accepted Answer

PMTiles is a single-file archive format for map tiles by Protomaps. geodebug.io reads the header via HTTP range requests, shows metadata (bounds, center, zoom range, vector_layers), and renders the tiles directly in your browser — no server required.

Question 4

What is the difference between TMS, XYZ, and WMTS tile schemes?

Accepted Answer

XYZ and TMS use the same tile pyramid but TMS flips the y-axis (origin at the bottom-left vs. XYZ's top-left). WMTS is the OGC standard with a GetCapabilities document that advertises layers, TileMatrixSets and resource URLs. geodebug.io supports all three and lets you toggle the y-flip to verify.

Question 5

How do I check if my tile server has CORS configured?

Accepted Answer

Paste the tile URL into the XYZ / TMS tab and click a Test fetch button. geodebug.io makes a CORS-mode fetch from your browser and shows the response status, Content-Type, and Content-Length. A network error or opaque response indicates missing Access-Control-Allow-Origin headers on the origin.