The short answer: running a song through this converter does not move any ownership to you. The copyright in the original recording and in the underlying composition belongs to whoever holds those rights, and it stays with them. What the conversion actually produces is a file on your own device — this tool runs entirely in your browser and uploads nothing, so the .mid never leaves your machine unless you send it somewhere — and whether you may share, post, sell, or sample that file is decided by the rights attached to the song you started from, not by the act of converting. This page sets out what can be stated as plain fact and where the answer depends on the song's own licence. It is general information, not legal advice.
What the converter actually produces
Before talking about rights, it helps to be exact about what comes out, because it changes the kind of copy we are discussing. A MIDI file stores notes — pitch numbers, start times, lengths and velocities — not a recording of the sound. This converter writes that out as a Standard MIDI File: one note track, one channel, no instrument assignment and no track names. There is no audio waveform in it and no melody you can play back without loading your own instrument in a DAW.
That matters for the ownership question in two ways. First, the .mid is a thin, abstracted transcription of the performance, not a clone of the recording — what What is actually inside a MIDI file walks through byte by byte. Second, because the detector reads pitch and timing from the whole signal, the output is still derived from the song you loaded, which is why it inherits the song's rights rather than escaping them. The technical shape of the file is neutral on the legal question; it only tells you what kind of derivative you have made.
The two rights that sit in every song
A finished track usually bundles two separate rights, and a converter touches neither of them — it only reads the audio you already have.
- The recording. The master — the actual audio file — is owned by whoever made and owns that specific recording (a label, an artist, a publisher). Loading it here does not change who owns it.
- The composition. The underlying work — the melody, the chords, the arrangement, the lyrics — is owned by the songwriter and their publisher, separately from the recording. A cover version can change the recording while the composition rights stay put.
Both of those rights exist independently of this tool. The converter is a reader of audio; it is not a party to either right and it grants you neither. That is the baseline every ownership question below has to start from.
Why the MIDI is a derivative of the source
The file you export is generated from the song, and its content — the notes and their timing — is a translation of the song's own musical material. That is what makes it a derivative work: it would not exist, and would not contain the notes it contains, without the source. Owning the derivative file locally does not dissolve the rights in what it was derived from.
None of this is special to this converter. It holds for any audio-to-MIDI step, because the output is always a transcription of someone's recording and composition. What is specific to this tool — and useful to know — is that the transcription never leaves your machine, which affects who has custody of the file but not the rights attached to its contents.
What this tool's browser-only design means for your copy
This converter runs entirely on your device. There is no upload endpoint, no account, and no server that stores your file or the result. The practical consequences for the ownership discussion are narrow but real:
- Custody stays with you. The .mid is written to your own download folder. No third party holds a copy that you would have to ask to delete.
- Nothing is redistributed by the service. Because the file is never sent anywhere, the converter is not a publisher of your output and does not put it into circulation.
- The right to use it is still not created here. Local custody is about where the file sits; it says nothing about whether sharing or selling it is permitted. Those questions go back to the song's recording and composition rights above.
In short, the architecture protects your privacy and your control of the file — the privacy page states the no-upload, no-account position in full — but it does not alter what you are allowed to do with a transcription of someone else's song.
A practical way to think about the chain
The cleanest mental model is a three-layer chain. The converter sits entirely in the last row and changes nothing in the first two:
| Layer | Who usually holds it | What the converter changes |
|---|---|---|
| The recording (the audio you load) | Label, artist, or whoever owns the master | Nothing — it stays on your device, never uploaded |
| The composition (melody, chords, lyrics) | Songwriter and publisher | Nothing — the tool only reads pitch and timing |
| The MIDI you export | A new file generated on your machine from the two above | You hold the local copy; your rights to use it ride on the two rows above |
Read it top down. If you do not own the first two layers, the third is yours to keep on your disk, but your freedom to push it outward is bounded by them. If you do own the first two — say it is your own recording of your own song — the third is straightforwardly yours too.
What you can usually do, and what depends on the song
Stated as plain fact rather than advice, the split looks like this:
- Keep and study it. Holding a transcription of a song you loaded, on your own device, for your own reference is the lowest-risk use and is what the converter is built for.
- Edit it locally. Transposing, cleaning, or re-instrumenting the .mid in your own DAW — the clean-up passes cover the common workflow — stays within your own use of the file.
- Share or release it. This is where the song's own licence decides. A transcription of a copyrighted song that you publish, sell, or feed into someone else's product is a use of the underlying work, and that needs a basis in the song's rights — a licence, a permission, or an applicable exception in your jurisdiction. The converter cannot supply that basis.
The honest line: the tool gives you a file and keeps it private; it does not give you the right to distribute what is inside it. Where that right comes from is a question about the song, asked of the song's owner or a qualified professional, not of the converter.
Questions people actually ask
Does converting a song to MIDI make it royalty-free?
No. Conversion is a change of file type, not a change of ownership. The recording and composition rights survive the conversion untouched. Nothing about turning an MP3 into a .mid grants you a licence to use the music, which is why MP3 to MIDI is about the notes, never about the rights.
Can I sell a MIDI I made from a popular song?
The ability to sell it depends on the composition and recording rights in that song, not on the converter. If you do not hold those rights or a licence covering commercial use, selling the transcription is a use of the underlying work. The converter produces the file; it does not create the permission to monetise it.
Isn't the MIDI just my own data, so it's mine?
The file on your disk is yours to keep, and because this tool runs in your browser with no upload, no one else holds a copy. But the contents of that file are a transcription of the song, so the rights in the song still govern what you may do with the contents. Local ownership of the file and permission to redistribute its contents are two different things.
Why does it matter that the tool runs in my browser?
Only for custody. With no upload and no account, the service never holds your file or your result, so it is not putting your output into circulation on your behalf. That is a privacy and control point — worth knowing — but it is independent of the copyright in the source song. Browser-only design changes who has the file, not what the file is allowed to be used for.
What about a song I wrote and recorded myself?
If you own both the recording and the composition, you own the MIDI too; converting it changes nothing about that. The whole discussion above is about material where someone else holds one or both layers. For your own work, the derivative is simply yours, and you can do with it what you like.
Does a full mix change the answer?
No. Whether the source is a single voice or a finished track, the ownership chain is the same — recording, composition, then your local derivative. A full mix just adds more rights-holders to the first two layers, which makes the “may I share this?” question more, not less, dependent on the song. Song to MIDI shows what that kind of input actually comes back as.
Convert a file now — it runs in your browser, nothing is uploaded, and the file that comes back is yours to keep.
Related guides
- MP3 to MIDIWhy MP3 loses notes that WAV keeps
- Song to MIDIWhat a full mix comes back as
- MIDI converterWhat is actually inside a MIDI file
- PrivacyWhy nothing you load is uploaded
- Clean up a converted MIDIThe 5 passes that turn a raw export into a usable part
- Mono vs polyWhat each detection mode misses
- AboutWhat this tool is and is not