Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As part of checking some prereqs for an idea (IOS app with MBtiles on local storage enabeling offline maps) I'd like to know if it's useful to gzip MBtiles when transporting them to an IOS device.

In other words, is there a useful reduction in size when gzipping MBtiles? (or is the MBtile-format, already packed in some way, thus limiting the use of gzip or other packers). If so, how much size reduction can I expect? (percentage ballpark)

NOTE: crosspost from SO (as it's within both domains)

share|improve this question
up vote 1 down vote accepted

If it's exported from TileMill, it'll be small - less than 15% on average, since you're dealing with PNG compression (internally similar to gzip) as well as a duplicate tile dictionary.

share|improve this answer
Thanks for responding here Tom. Question was meant generally, but I'm particularly thinking of the default Mapbox streets layer. So I guess I'm talking to the right person ;). Just realized (duh) that I could just inspect my client request/responses to get some real feel of sizes. 25KB/tile for levels 13-16 and 15-20KB/tile for level 17 seems to be average. And being served as png indeed no use for gzip. Checking now if (guessing yes) untoggling buildings makes a big impact on size. Thanks. – Geert-Jan Dec 13 '12 at 17:44
yup.. disabling buildings -> ~6KB/tile on level 17. great – Geert-Jan Dec 13 '12 at 17:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.