WebMIDI Keyboard Tester

Test a USB MIDI keyboard, synth, pad controller, pitch wheel, modulation wheel, note velocity, and stuck notes directly in the browser with Web MIDI.

Ready to request MIDI access
Device detected No MIDI device selected Input: none
Visible range: C3-B5

Velocity curve

MIDI event log

  • Play a key or move a wheel to see incoming MIDI messages.
Zoom 100%
Utilities Studio

Want this utility on your website?

Customize colors and dark mode for WordPress, Notion or your own site.

Frequently Asked Questions

Can this MIDI keyboard tester read my USB keyboard without installing software?

Yes, in browsers that support Web MIDI, such as Chrome and Edge. The browser asks for permission, then the tool listens to note, velocity, pitch bend, and modulation messages from the selected MIDI input.

Does the website upload my MIDI notes or performance data?

No. MIDI events are processed in the current browser tab. Notes, velocity values, controller messages, device names, and logs are not uploaded or stored by the website.

Why does my MIDI keyboard appear but no keys light up?

The device may be connected as a control surface, the wrong input port may be selected by the browser, the keyboard may be using a different mode, or the cable/hub may be passing power but not MIDI data.

Can I test pitch bend and modulation wheels?

Yes. The tester shows pitch bend as a centered signed value and modulation as MIDI CC1. Moving those controls should update their meters immediately when the device sends standard MIDI messages.

Which MIDI messages are shown?

The live interface highlights Note On and Note Off messages, records velocity, detects pitch bend, and tracks modulation wheel CC1. Other controller messages may appear in the event log when they are relevant to the tested controls.

# MIDI Keyboard Tester Online for Real USB Hardware

A reliable MIDI keyboard tester online should answer one question quickly: is the physical instrument sending the messages a DAW, sampler, synth, or lighting rig expects? This WebMIDI tester listens to the browser MIDI input and shows Note On, Note Off, velocity, pitch bend, and modulation wheel data in real time. It is designed for USB MIDI keyboards, DIN-to-USB interfaces, synthesizers, pad controllers, stage pianos, MIDI guitars, drum triggers, and compact controllers used in home studios or live rigs.
Private local MIDI diagnostics
The test runs entirely client-side. The website does not upload note numbers, velocity curves, controller movement, device names, or event logs. The browser exposes MIDI only after you approve the permission prompt, and the values remain in the current tab.
0-127 MIDI velocity range
128 standard note numbers
14-bit pitch bend resolution
CC1 modulation wheel control
Signal What the tester displays Healthy behavior
Note OnKey name, note number, channel, and velocity.Each physical key lights once when pressed and uses a velocity value above zero.
Note OffRelease event in the log and key light reset.Every pressed key clears when released; no notes remain visually stuck.
VelocityLive meter plus a rolling curve.Soft playing produces lower values and firm playing reaches higher values without random jumps.
Pitch bendCentered signed meter from negative to positive.The wheel sweeps smoothly and returns close to zero when released.
ModulationCC1 meter from 0 to 127.The wheel or strip moves predictably through the full range.

# How to Probar Teclado MIDI Without a DAW

Searching for probar teclado MIDI often means the user does not yet know whether the failure is the controller, the cable, the operating system, or the music software. A DAW adds many extra variables: track arm state, input filters, MIDI channel routing, virtual instruments, monitoring, templates, and driver preferences. A browser tester removes most of that stack. If the WebMIDI permission prompt sees the device and the keyboard lights notes on screen, the physical MIDI path is alive.

Use this before changing DAW settings

Worth noting
First confirm that the controller sends raw MIDI. Then troubleshoot the music application. If the tester receives notes but the DAW does not, inspect MIDI input enablement, selected track input, channel filters, control-surface scripts, and instrument monitoring.
  • Connect the keyboard directly to the computer when possible, especially if bus power is marginal.
  • Open the tester in Chrome or Edge, because Web MIDI support varies by browser and platform.
  • Press Connect MIDI Input and choose the musical device or MIDI interface from the permission prompt.
  • Play chromatic notes across the keyboard to reveal dead keys, split zones, or octave transpose surprises.
  • Move the pitch and modulation wheels slowly, then quickly, to catch noisy sensors or poor return-to-center behavior.
  • Clear the log between tests when comparing cables, USB ports, keyboard presets, or controller modes.
Fast cable check
If the device powers on but no MIDI input appears, try a different USB cable. Many cheap USB cables are charge-only and do not carry data, which makes a controller look alive while no MIDI messages can reach the computer.

# Reading Velocity Curves and Dynamic Response

Velocity is not loudness by itself; it is a performance value sent with a note, usually from 1 to 127. A piano plugin may map velocity to volume, sample layer, brightness, hammer noise, attack time, or all of those at once. When a controller has poor velocity scanning, a player may feel that soft notes disappear, medium notes are too loud, or hard notes never reach the expressive top layer. The rolling velocity curve helps reveal whether the hardware produces a usable spread of values.

Healthy keybed

Soft, medium, and hard strikes produce visibly different velocity bands with repeatable values for similar playing force.

Compressed response

Most notes cluster in a narrow range, such as 70-95, making piano and drum instruments feel flat or difficult to control.

Erratic response

Adjacent notes or repeated strikes jump unpredictably, suggesting dirty contacts, failing sensors, bad scanning, or unstable firmware.

Observed velocity pattern Likely interpretation Next test
Always 127Fixed-velocity mode is enabled or the controller is configured for organ/synth triggering.Check the keyboard global settings, pad mode, or controller editor.
Always very lowVelocity curve is too soft, sensor calibration is wrong, or the keybed is failing.Switch velocity curves and compare black/white keys across octaves.
One key differs sharplyA local contact, rubber dome, optical sensor, or key mechanism may be dirty or damaged.Repeat that key at several strengths and compare neighboring notes.
Values drop after a hub is usedPower or data stability may be marginal.Retest with a direct USB port and a known data cable.

Why Note Off matters

A stuck note is often a missing or delayed Note Off message. Some instruments send Note On with velocity 0 instead of a separate Note Off command; both are valid MIDI behavior. This tester treats velocity-zero Note On as note release, so genuinely stuck keys remain visible until the correct release message arrives.

# Testing Pitch Bend, Modulation, and Performance Controls

Pitch bend is a higher-resolution MIDI message than ordinary 7-bit controller data. It combines two data bytes into a 14-bit range centered around 8192. That extra resolution matters because pitch movement should sound smooth, especially when bending a lead synth, bass, or orchestral instrument. The tester converts the incoming bend to a centered meter, making it easy to see whether the wheel reaches both extremes and returns to neutral.The modulation wheel is normally MIDI continuous controller 1, commonly written as CC1. Many synth patches use it for vibrato, filter movement, wavetable position, tremolo, or orchestral dynamics. If moving the wheel does not update the CC1 meter, the controller may be assigned to a different CC, using a vendor-specific mode, or routed through software that remaps performance controls.

Browser MIDI test versus DAW monitoring

Advantages
  • Fast permission-based hardware confirmation with no project setup.
  • Clear view of notes, velocity, pitch bend, and CC1 modulation.
  • Good for support calls, buying used gear, and checking cables.
Disadvantages
  • It does not emulate every DAW routing, script, or instrument mapping.
  • Advanced aftertouch, NRPN, MPE, SysEx, and custom control maps may need specialist tools.
  • Browser support depends on Web MIDI availability on the current platform.

Pitch wheel does not return to zero

Warning
If the pitch meter rests at a positive or negative value after release, the physical wheel, spring, potentiometer, hall sensor, calibration, or firmware deadband may need attention. Test the same controller in another port and preset before assuming the sensor is faulty.

# Common MIDI Keyboard Faults This Tester Can Reveal

Dead key
A physical key that produces no Note On message when pressed.
Stuck note
A note that receives Note On but no matching release message, leaving the sound active in instruments.
Velocity spike
A sudden value much higher or lower than expected for a similar strike.
MIDI channel
One of 16 logical channels used to separate parts, zones, or devices on a MIDI stream.
Control Change
A MIDI message family used by knobs, pedals, wheels, sliders, and switches.

Device detected, no messages

Critical issue
If the browser lists a MIDI input but playing keys produces no log entries, check whether the selected port is a control-surface input instead of the keyboard note input. Some interfaces expose multiple ports with similar names.
Symptom Possible cause Practical action
No permission promptUnsupported browser, insecure origin, or blocked browser MIDI permission.Use Chrome/Edge over HTTPS and inspect site permissions.
Device missingCable, hub, driver, class-compliance, or power problem.Try another USB data cable, port, or powered hub.
Only some octaves workSplit/layer mode, transpose setting, hardware matrix fault, or local control mode.Reset the preset and test chromatically from low to high notes.
Wrong pitch namesThe controller is transposed or sending from a zone with octave shift.Check global transpose, zone octave, and DAW template settings.
Mod wheel silentWheel assigned to a different controller number or disabled by preset.Load a default preset or controller editor and map it back to CC1.

Best diagnostic order

Confirm the browser sees the MIDI input.
Play notes and verify matching press/release behavior.
Inspect velocity distribution with repeated soft, medium, and hard strikes.
Move pitch bend and modulation controls through their full travel.
Only then adjust DAW routing, virtual instrument settings, or controller templates.

# Privacy, Browser Support, and Limits

Web MIDI is intentionally permission-gated. A page cannot silently read connected musical devices in the background without the browser exposing an access flow. The exact prompt and persistence of permission depend on browser, operating system, and user settings. For most musicians, the practical result is simple: click the connect button, choose the MIDI input, run the test, and close the tab when finished.
  • No MIDI event data is sent to any external server.
  • The tester does not require SysEx access, which keeps the permission scope narrower.
  • Device names shown by the browser can identify hardware models, so screenshots should be shared thoughtfully.
  • Chrome and Edge generally provide the best Web MIDI support; Safari and Firefox support can be limited or absent depending on platform.
  • Native utilities may still be needed for firmware updates, deep controller editing, MPE analysis, SysEx dumps, or vendor-specific diagnostics.

When this tool is enough

For buying a used controller, checking a studio cable, validating a USB MIDI interface, testing a repaired keybed, or proving that a keyboard sends messages before opening a DAW, a WebMIDI keyboard tester is usually the fastest first step.

Bibliographic References