Build interactive 2D maps, game boards, pixel editors, minimaps, and large data grids with a renderer-agnostic TypeScript engine. Canvas Tile Engine supports Canvas2D, WebGL, React, React Native (Skia), and server-side rendering, providing a unified API with pan/zoom, layers, sprites, viewport culling, and high-performance rendering across platforms.
No reviews yetBe the first to leave a review for Canvas Tile Engine – Maps,Grids&Editors
Maker
📌
Hi everyone! I’m excited to share Canvas Tile Engine.
I built it after repeatedly needing the same core features—camera controls, pan/zoom, layers, tile rendering, and pointer interactions—for grid-based applications. Existing solutions were often tied to a single renderer or focused on full game engines, while I wanted a lightweight, reusable rendering engine.
Canvas Tile Engine provides a unified TypeScript API across Canvas2D, WebGL, React, React Native (Skia), and server-side rendering, making it easy to build interactive maps, game boards, pixel editors, minimaps, and large data grids.
I’d love your feedback on the API, documentation, performance, and developer experience. Feature requests and contributions are always welcome. Thanks for checking it out!
Report
Does it handle really large grids like 10k x 10k without choking, and what happens if I need to swap renderers later in the project?
Report
Rendered a pretty large tile map with layers and pan/zoom running smoothly on both Canvas2D and WebGL with no API changes needed. The renderer-agnostic approach is genuinely useful for cross-platform work.
Report
Been messing around with the viewport culling on a pretty big map and it's holding up really well, no dropped frames even when zooming fast. The unified API across Canvas2D and WebGL made switching renderers way less painful than I expected.
Report
The renderer-agnostic API is a really smart move, makes swapping between Canvas2D and WebGL painless. Caught me off guard how smooth the pan and zoom felt even on a pretty dense grid.
Report
Finally a tiles API that doesn't lock you into canvas2d. The pan/zoom layer culling feels really solid and switching to WebGL was just a one-line change.
Does it handle really large grids like 10k x 10k without choking, and what happens if I need to swap renderers later in the project?
Rendered a pretty large tile map with layers and pan/zoom running smoothly on both Canvas2D and WebGL with no API changes needed. The renderer-agnostic approach is genuinely useful for cross-platform work.
Been messing around with the viewport culling on a pretty big map and it's holding up really well, no dropped frames even when zooming fast. The unified API across Canvas2D and WebGL made switching renderers way less painful than I expected.
The renderer-agnostic API is a really smart move, makes swapping between Canvas2D and WebGL painless. Caught me off guard how smooth the pan and zoom felt even on a pretty dense grid.
Finally a tiles API that doesn't lock you into canvas2d. The pan/zoom layer culling feels really solid and switching to WebGL was just a one-line change.