Is my proprietary code or map file secure?

Yes, 100%. All file parsing and visualization run completely inside your web browser locally. No code, map files, or proprietary project structure data are ever uploaded to any external server.

Does it support EWARM project virtual folder structures?

Yes. By dropping both your project file (.ewp) and linker map file (.map), IAR Map Visualizer maps compiled object files directly to your virtual IDE folder hierarchy.

How can I set a custom Target Flash memory budget?

In the sidebar settings, you can enter your microcontroller's Flash memory capacity (in KB or MB). The tool immediately calculates total ROM footprint utilization percentages and remaining available space.

IAR Map Visualizer - EWARM Linker Map & Memory Footprint Analyzer

Get Started

Drop your IAR Embedded Workbench linker map file (.map) and project file (.ewp) below. All parsing happens locally in your browser—your proprietary code files never leave your computer.

Drag & drop your EWARM .map or .ewp files here

or click to browse your local filesystem (select both .map & .ewp)

Or Evaluate Instantly

ROM & RAM Treemap Visualization

Visualizes Flash memory footprint (RO Code & RO Data) and RAM consumption (RW Data) proportionally. Drill down through modules and libraries with real-time dynamic rendering.

EWARM Virtual Project Folders

Full support for IAR Embedded Workbench project files (.ewp). Group memory usage according to your virtual IDE folder structure or build output libraries.

100% Private & Offline Processing

All map file parsing executes strictly inside your local browser. Proprietary C/C++ build artifacts never leave your machine, ensuring full corporate compliance.

Flash Budget & Area Breakdown

Set custom MCU Flash size limits (KB/MB) and track memory headroom. Split treemaps across discrete memory regions like Internal Flash, QSPI, and SRAM.

Frequently Asked Questions

What is IAR Map Visualizer?

IAR Map Visualizer is a free, web-based tool designed to parse linker map files (.map) and project files (.ewp) from IAR Embedded Workbench for ARM (EWARM). It converts raw text memory tables into intuitive, interactive treemap charts for memory optimization in embedded systems.

How does client-side parsing protect source code privacy?

Unlike traditional web tools, all parsing algorithms are written in pure client-side JavaScript. Your file data remains within your browser's memory sandbox and is never uploaded over network requests.

How do I generate a map file in IAR EWARM?

In IAR Embedded Workbench, open your project options, navigate to Linker > List, and check Generate linker map file. Rebuild your project to generate the .map output file.

概要（日本語）

IAR Map Visualizer は、IAR Embedded Workbench for ARM (EWARM) のリンカーマップファイル（.map）およびプロジェクトファイル（.ewp）をブラウザ上で解析し、ROM (RO Code/Data) および RAM (RW Data) のメモリ使用量を視覚的に可視化するWebツールです。すべての処理はブラウザ内でローカル実行されるため、セキュリティ面も安心です。

Drop .map or .ewp file to update current analysis

Loaded Workspace

Map File: None

EWP Project: None

Target Flash Size

Flash Memory Capacity

ROM Utilization 0%

0 B / 256 KB

Navigation Tips

Use EWARM Folders mode to group modules by your IDE virtual project folders.
Click on a group or folder node to drill down into child nodes.
Hover over elements to see detailed code, read-only data, and RAM breakdowns.
Use the breadcrumb bar at the bottom of the chart to navigate back up.
Search in the table below to filter objects, and click a row to locate it.

Total ROM Footprint

0 B

RO Executable Code

0 B

0% of ROM

RO Constant Data

0 B

0% of ROM

RAM Consumption (RW)

0 B

0 bytes

ROM Treemap Visualizer

Size represents ROM size (ro code + ro data)

Grouping:

ROM Areas:

RAM (RW Data) Treemap Visualizer

Size represents RAM size (rw data)

Grouping:

RAM Areas:

RAM Address Placement Grid

Vertical: 0x1000 base | Horizontal: 0x0000–0x0FFF offsets

Displays RAM module (.o) address placement. Each row represents a 4KB (0x1000) memory page block, and horizontal blocks depict .o module footprints from 0x0000 to 0x0FFF address offset.

Base Address

0x0000 0x0400 0x0800 0x0C00 0x0FFF

Object Module Details

Library/Group	Module (.o)	RO Code (B)	RO Data (B)	RW Data (B)	ROM Size (B)	ROM %