How to Open and Inspect a Model in Netron

To inspect a model in Netron, open the site in a browser, use the Open Model entry to select a local model file, then read the resulting graph view: nodes represent layers or operations, and the connections between them show how data flows through the model. This works for any model file Netron can parse, and the file stays on your machine — you are picking a local file, not uploading it to a server for processing.

Before you start

• A model file already saved on your computer (for example, an exported .onnx, .pt, or similar file — the exact formats Netron accepts are covered in the separate question on supported formats).
• A modern browser. Netron runs in the page, so no installation step is described here.
• Know roughly what you expect to see: the number of layers, the input shape, or a specific operator name. This makes it much easier to confirm the graph loaded correctly.

Step-by-step: open a model

1. Load the page. Go to netron.app. The landing view shows a mostly empty canvas with the Open Model control.
2. Choose your file. Click Open Model and pick the model file from your local disk. The browser's file picker is what selects the file; Netron reads it directly.
3. Wait for rendering. Netron parses the file and draws the graph. Small models appear almost instantly; large ones take longer because every node and edge must be laid out.
4. Confirm it loaded. You should see a connected graph of boxes rather than an error message or a blank canvas.

Expected result: a scrollable, zoomable diagram of your model's architecture.

Reading the graph view

The graph is the main inspection surface. What to look at, in order:

Nodes

Each box is a layer or operation. Clicking a node typically reveals its properties — type, name, and attributes such as kernel size or activation. Use this to check that a layer you expected is actually present and configured as intended.

Connections

The lines between nodes are tensors flowing from one operation to the next. Follow them to trace the path from input to output. Branching lines indicate where a tensor is consumed by more than one downstream node — useful for spotting skip connections or shared weights.

Inputs and outputs

The first and last nodes tell you the model's expected input and produced output. Compare the input shape against what your data pipeline will supply; a mismatch here is one of the most common reasons a model fails downstream.

Navigation

Zoom and pan to move around large graphs. For deep models, work section by section rather than trying to read the whole diagram at once.

Version and legend information

The interface includes a version label (shown as Version {version}) and a legend explaining the symbols used in the graph — for example, the small markers that distinguish different node or edge types. Check the legend first if a symbol in the graph is unfamiliar; it saves guessing. The version label is also worth noting if you are comparing behavior across releases or reporting an issue.

Common sticking points

When this approach fits

Use the browser-based route when you want a quick structural check — confirming layer order, tracing connections, or verifying an export before handing the model to someone else. If you need to compare two versions of a model side by side, open them in separate browser tabs and switch between them; the graph view is read-only, so inspection does not alter your file.