Map Viewer

What Map Viewer does

Map Viewer renders a rectangular set of decimal or 0x-prefixed hexadecimal byte values as a labeled table with a relative heatmap. It can help inspect a region you have already selected; it does not search a full binary, use byte offsets, identify map boundaries, or verify ECU meaning.

Input and limits

• Enter one table row per line. Use decimal integers from 0 to 255 or hexadecimal bytes prefixed with 0x; separate values with spaces or commas.
• All rows need the same number of values. Optional headers use “# AxisName label1 label2 …”; header label counts must match table dimensions.
• Input is limited to 256 rows, 256 columns, 16,384 byte values, and 256,000 characters. Oversized or malformed input is rejected before rendering.

View, edit, and export

Render a source table before using view controls. Transpose changes the displayed orientation; color themes show relative values while the byte values remain available as text. Edit mode changes the in-browser result only. Individual edits accept whole decimal bytes from 0 to 255; undo, redo, and Revert edits work on the current rendered source. Reset view restores display controls without discarding data.

CSV and JSON downloads represent the current edited result; JSON preserves the original table when edits are present. SVG is a visual snapshot. These outputs are not verified calibration files.

Map Extractor and data handling

Map Extractor validates and labels a selected rectangular byte region, then passes it to Map Viewer in this browser. Map Viewer also keeps the last input and up to five recent inputs in browser storage. Processing and edits are local. If you create or share a link, its URL contains the current map data and label.

A share link contains the current map values, axis labels, and map label in its URL. Anyone who receives the link can read that data, and it may remain in browser history or other places where URLs are stored. Generated links are limited to 8,000 characters and are not private. The link does not include view settings, selection, or undo history.

Interpretation and limitations

The table and heatmap visualize supplied numbers only. They do not establish byte order, scaling, map type, ECU compatibility, or safety. Scale and offset operations round to whole bytes and clamp to the byte range. Do not treat a rendered or edited table as confirmed calibration or as suitable to flash to a vehicle.

Related tools and learning

• Map Extractor formats a selected byte region and checks its rectangular shape before hand-off.
• Working with Raw ECU Files introduces binary structure and selected regions.
• Creating and Smoothing Custom Maps discusses map dimensions and table editing concepts.
• Tuning Strategies: Map Scaling introduces map-scaling concepts; this viewer’s byte transform is not a substitute for verified calibration scaling.