ANDROID BROWSER WORKFLOW
On an Android phone, open this page in a browser, tap Choose audio, select one saved MP3 or other listed format, then tap Convert to MIDI and Download .mid. The file is decoded and analyzed on your device. If the audio cannot be decoded, the format label alone does not make it compatible. To find a completed download in Chrome for Android, check Chrome Downloads or the Files app.
TEST YOUR FILE
Select one audio file, inspect the result, then save the .mid.
INPUT MP3 / WAV / M4A / FLAC / OGG → OUTPUT .MID
or click to choose audio from your device
MP3, WAV, M4A, FLAC, or OGG · one file · up to 50 MB / 5 minutesRESULT
Your audio stays on your device. All processing happens in this browser. No file is uploaded to a server.
PICK THE FILE
Tap the upload area and select one actual MP3, WAV, M4A, FLAC, or OGG file from the phone's picker. The page checks the extension and size first. It then calls the browser's audio decoder on the full file. An accepted extension is therefore only the first gate; a file with an unsupported encoding can still fail to open. MDN's decoder reference explains this browser step.
SAVE THE RESULT
After the note preview appears, tap Download .mid. The script creates a MIDI Blob and asks the browser to save it with the source filename plus a .mid extension. Google Chrome Help for Android says completed downloads can be found in the Files app and Chrome's Downloads list. Actual storage prompts and file locations can vary by browser and phone.
This checklist follows the current page code. It describes what you can verify in your own browser, not a claim that every Android model or audio codec has been tested here.
| Stage | What the page checks | Visible signal | Next action if it stops |
|---|---|---|---|
| Selection | One file with a listed extension | The file card shows its name | Choose the actual audio export, not a renamed file |
| Size | File no larger than 50 MB | No over-limit message | Use a shorter or smaller genuine audio file |
| Decode | Browser can decode the complete file; decoded duration no longer than 5 minutes | Ready to analyze; Convert button enabled | Try a real standard PCM WAV or MP3 export |
| Result | Detector finds notes and MIDI writer returns bytes | Result panel and Download .mid button | Listen to the source; test a clearer single-note segment |
Download this original gate checklist (.csv). For a real download check, open the resulting .mid from Chrome Downloads or Files; the page cannot see where Android saved it.
BEFORE RETRYING
“This browser could not decode that file” occurs before pitch analysis. Changing Silence threshold, Pitch range, or Minimum note cannot repair that decode failure. Once the status says Ready to analyze, those controls affect note detection; compare the preview against one clear melody before changing them.
TESTED SCOPE
The site's source code shows a local file read, Web Audio decode, note analysis, and a browser download request. A desktop browser at phone width can check whether the controls fit the screen, but it does not prove the Android file picker or download manager behavior on your device. Use the status messages above to identify your own stopping point.
QUICK ANSWERS
No. The current script reads the selected file into this browser's audio context and analyzes it locally. The MIDI download is created in the browser.
The selected file must finish decoding. If the page shows a decode error or an over-limit message, choose a genuine supported export within the displayed limits.
Check the browser's Downloads list and the phone's Files app. Google Chrome Help documents both routes; the exact location depends on your browser and device settings.
No guarantee. The page accepts those extensions, but your browser still must decode the actual audio encoding. If it fails, export a real MP3 or standard PCM WAV copy and retry.
No. This detector follows one dominant pitch at a time. Choose a clear isolated melody for a meaningful first test.