MIDI Inspector

Inspect MIDI events, tracks, channels, tempo changes, and note issues locally in your browser — no uploads.

Works locally · No account required · Great for debugging timing, tracks, and controllers

English 中文 Deutsch
MIDI → JSON MIDI → CSV MIDI Inspector Pro Blog

Drop a MIDI file here

or

No file selected

Unlock Pro — $9.90 lifetime
One purchase unlocks Pro across all MidiEasy tools.

Upgrade to Pro — $9.90 Lifetime

Pro See all Pro features →

One purchase unlocks Pro across all MidiEasy tools.

How to upgrade

Step 1 — Buy
Buy Pro (Lifetime) — $9.90

You’ll receive a Stripe receipt. Come back here to activate in 5 seconds.

Step 2 — Activate

Use the email shown on your Stripe receipt.

Pro Benefits

On this page
    Also includes
    • One purchase, unlock Pro across all MidiEasy tools.
    • Local processing. No uploads.
    • Activate with checkout email. No account.
    • Up to 2 devices.

    FAQ

    Why do I need to activate after purchase?

    Activation links your checkout email to this device (up to 2 devices) — no account needed.

    Is it safe?

    Payments are handled by Stripe. We only verify your email for Pro.

    Does Pro work on all tools?

    Yes. Pro is a site-wide upgrade — once activated, it applies across all MidiEasy tools.

    I hit the 2-device limit — what now?

    Email us at support@midieasy.com and we’ll reset your devices.

    What This MIDI Inspector Checks

    This MIDI Inspector helps you understand how a MIDI file is structured before you export or edit anything.

    Events & controllers

    Tempo, time signature, program changes, control changes, noteOn/noteOff, and CC64 sustain events.

    Tracks & channels

    See whether a file is single-track or multi-track, and how channels/programs are distributed.

    Tempo & timing structure

    Inspect PPQ, ticks, seconds, tempo events, and time signature changes to debug timing mismatches.

    Note integrity & quality flags

    Spot overlap, dangling notes, orphan note-offs, and other issues that can break playback or analysis.

    If you need to debug MIDI before exporting it to CSV or JSON, this is the fastest place to start.

    Example Inspection Output

    Here is what a real MIDI file can look like inside the inspector. Example file: Catch A Fire.

    MIDI Inspector summary cards showing duration, PPQ, tracks, notes, tempo events, and quality metrics.
    Summary cards
    MIDI Inspector Events tab listing tempo, time signature, and program rows for timing and structure debugging.
    Events view
    MIDI Inspector Tracks tab showing track endTick, note count, channels, and programs.
    Tracks view
    MIDI Inspector Notes tab with note-level rows including channel, program, pitch, start tick, duration, and velocity.
    Notes view (with note rows)

    How to Inspect a MIDI File

    Load one file, inspect multiple views, then filter to isolate timing, structure, and note issues.

    1

    Load your MIDI file

    Drop a MIDI file into the inspector to see its structure instantly. Processing runs locally in your browser.

    2

    Switch views

    Use Events, Tracks, and Notes to inspect different layers of the file.

    3

    Filter what matters

    Filter by track, channel, pitch, controller type, or quality flags to narrow down timing, note, or controller issues.

    Start with Events for tempo/program changes, use Tracks for structure, and use Notes for note-level detail.

    Common MIDI Debugging Scenarios

    Problem-first checks for the most common MIDI inspection questions.

    Why is track always 1?

    Many MIDI files are single-track. In that case, track stays 1 even when multiple channels and programs exist.

    Next step: Export notes to CSV

    Why does timing look wrong?

    Timing mismatches often come from tempo events, time signature changes, or mixing up ticks and seconds.

    Next step: Read the timing guide

    Why do I see so many channels?

    A single track can still contain many channels. Use track + channel + program together to map parts and instruments.

    Next step: Convert inspected MIDI to CSV

    How do I inspect sustain pedal events?

    Sustain is usually stored as CC64. Use the event filters and keep CC64 rows visible when debugging playback feel.

    Next step: Inspect controller events

    What do overlap and dangling notes mean?

    These flags identify note integrity issues that can affect playback, visualization, or downstream export.

    Next step: Upgrade for advanced note filtering

    What are unknown events?

    Some files include uncommon or device-specific events. Review quality summary + event list before exporting.

    Next step: Inspect events

    Quality Flags Explained

    Quality flags help you find structural issues in note data before exporting or editing a MIDI file.

    If you are debugging playback, note integrity, or export quality, flags are often the fastest place to look.

    When to Use Inspector vs CSV vs JSON

    Pick the right tool based on whether you are debugging structure, analyzing notes, or building with structured output.

    Need Best tool
    Debug tracks, channels, tempo, events, or note issues MIDI Inspector
    Analyze notes in Sheets / Excel MIDI to CSV
    Work with structured output in code MIDI to JSON

    Use Inspector first when something looks wrong. Use CSV for spreadsheet analysis, and use JSON for scripts, web apps, or pipelines.

    Export inspected notes to CSV Convert inspected MIDI to JSON

    Frequently Asked Questions

    Quick answers for event inspection, track/channel logic, timing checks, and quality flags.

    It shows MIDI events, tracks, channels, notes, tempo changes, time signatures, and quality indicators such as overlap or dangling notes.

    No. Inspection runs locally in your browser. Your MIDI files stay on your device.

    Many MIDI files are single-track. In that case, channels and programs are often the best way to distinguish parts.

    A track is part of the file structure. A channel is a MIDI routing layer often used for instruments or parts. One track can contain many channels.

    Open the Events view and look for tempo and timeSig rows.

    They are note integrity flags that help identify structural problems in note data.

    Use Inspector when you need to debug structure or events. Use CSV when you want note-level analysis in spreadsheets.

    Latest Guides

    Learn how to inspect, export, and debug MIDI data more effectively.

    How to Convert MIDI to CSV (Examples + Common Issues)

    March 2, 2026

    Read More

    MIDI to JSON Conversion Guide

    March 15, 2025

    Read More

    Web Music Application Development

    February 28, 2025

    Read More
    View All Articles