Tool · Map Editors
Map Scale Adjuster
Apply a percentage or signed offset to a rectangular table of unsigned byte values, then review rounding and 0–255 clamping.
Adjust a decimal byte table
Enter rectangular rows of unsigned decimal 8-bit integers (0–255), separated by spaces or tabs. Blank lines between rows and commas are not supported. Limit: 256 rows, 256 columns per row, 16,384 values and 256,000 characters.
No current result. Editing the table or adjustment clears the previous result.
How scaling and offsets work
Scaling multiplies each source value by the percentage divided by 100; for example, 100 at 110% becomes 110. An offset adds or subtracts the entered amount; 100 with −5 becomes 95. Results are rounded to whole integers, then clamped to the unsigned 8-bit output range 0–255.
Input values are treated as unsigned decimal bytes. This tool does not interpret multi-byte words, signed encodings, byte order, units, map axes, or ECU scaling metadata. The arithmetic is an educational table transformation; it does not identify a map or establish that a calibration is safe or suitable for a vehicle.
See Tuning Strategies & Map Scaling for related learning. Verify the meaning and encoding of any values before using them in another workflow.
A synthetic rounding and clamping example
For supplied unsigned byte values 41 and 250 at 110%, the calculations are 41 × 1.10 = 45.1 → 45 after rounding and 250 × 1.10 = 275 → 255 after clamping to the byte range. These example values have no assigned unit or calibration meaning.
The tool performs arithmetic on supplied byte values. It does not apply verified calibration scaling or establish what a value means in an ECU. See the byte-table scaling lesson for the operation order and the synthetic table workflow Guide for how selected values become a table.