Export Clean Grid Page

I was surprised this wasn't basic functionality. I would like the ability to export the custom set grid of a Roll20 page with the appropriate margins and number of squares/hexes to edit in an external image program. No assets, no tokens, not even the background and map. I just need the grid and the margins.

This would simplify my map-making workflow immensely, since I don't have and don't want any of the more powerful custom dungeon-building programs. I just need an image I can open up in my art programs to use as a guide for another layer. That way when I import it to the page it was exported from and fit it, it, all my custom drawn battle-map will line up automatically with the page without any need to do any fussy resizing.

To reiterate, the exported grid can be any functional resolution, I won't be importing the grid itself back into Roll20, just the image based on the grid. The existing Roll20 grid and grid-snap functions should work perfectly with this custom made battlemap.

Most requests for exporting Roll20 pages seem to run afoul the concern of exporting paid content or assets. I do not need any assets to be exported, paid or otherwise, I just need the grid and the margins.

Thank you for your time, I hope to see this suggestion implemented.

Keeping in mind that the default display in Roll20 is 70 pixels per grid square, you can make any map you like in an any external image editing program that measures in pixels. Then you just upload it to Roll20 and size the Roll20 page to match the size you designed the map to.

Keep in mind that you may want to make a map at 140 pixels per square to allow greater detail when zooming in. Beware though: too much detail can increase file size and lag, with very little benefit (to the human naked eye). It's a balancing act.

You can read more about image best practices in the Wiki: https://wiki.roll20.net/Image_Best_Practices_for_Roll20

This is fine, but matching to a nonstandard grid size or to existing tokens would be easier if an export function was present. Resizing functions are adequate, but require additional legwork.

I have already viewed the best practices page. The process I've outlined would still simplify asset creation and design, especially regarding exact grid matches and size, which can be a much more involved problem in hex-grid aligned mapping.

Thanks for the suggestion!

After 30 days, Suggestions and Ideas with fewer than 10 votes are closed and the votes are refunded to promote freshness.

Your suggestion didn't build the right momentum this time, but feel free to submit it again! We find that the best suggestions describe the problem you are having, and the solution you want. You can learn more about the process of making suggestions on the Roll20 Wiki! More details can be found here.