Live match · your PC
Draws the real tactical map from your running War Thunder client (map.img + live objects on localhost:8111). No offline atlas, no invented boards.
While you are in a battle, the game serves map.img and map_obj.json on loopback. This page reads that feed in your browser and paints it. We do not host or invent static map art.
The WT Charts Map Tool is a live companion for War Thunder battles on your PC. It reads the same localhost feed the game opens during a match and draws the real tactical map — not a hand-drawn atlas, and not a scraped gallery of minimaps.
When War Thunder is running and you are in a battle, the client hosts a small HTTP service on 127.0.0.1:8111. That service exposes map.img (the tactical bitmap), map_obj.json (units, airfields, capture points, respawns), map_info.json (grid bounds), and mission.json (objective text). This page asks those endpoints from your browser and paints the result.
Because the feed is loopback-only, WT Charts servers never see your match. The overlay only works on the same computer as the game client. Phones, tablets, and second PCs cannot reach your local 8111 port.
Static “useful position” boards are easy to fake and hard to verify. Spawn layouts change with mission variants, and hosting ripped in-game art without a clear license is a poor foundation for a tools site. Until we can wire real CDK or wiki map assets with honest attribution, this tool stays live-only.
If you need map theory offline, use the official War Thunder wiki map pages or the CDK asset viewer. Use this page when you are actually in a fight and want the live board plus object markers.
Launch War Thunder on this PC, queue into a battle, keep this tab open, then poll once or enable 1-second refresh. Pan and zoom the canvas to inspect airfields, caps, and unit markers from map_obj. Mission text appears when mission.json is available.
HTTPS deployments sometimes block mixed content to localhost. Allow local-network access in the browser, or test on HTTP localhost during development. Partial errors usually mean you are still in the hangar or the browser blocked one of the endpoints.