MP3 to MIDI by Audio Source: What Each Converter's Terms Allow
Every converter answers the same question differently: what does this service claim over the audio I hand it? That answer, not copyright, decides which sources you can use.
The short answer
- Ask the terms question, not the copyright question. Only one of the two has a written answer.
- Three vendors, three positions. One never receives the file on its free path; one takes a training licence over anything you post; one excludes training on its API.
- One vendor gives two answers: its web page and its API run under different documents.
- Only one of the three limits what you may do with the output.
- None says what to keep as evidence of your right to the audio.
- No benchmark site compares these positions.
The sentence all three lead with
ai-midi's FAQ tells users to secure copyright clearance. jukeblocks' terms call uploading copyrighted content without permission misuse. songscription says the same in parentheses: for audio you have the right to use.
Identical everywhere, and it decides nothing: what decides is what happens after the upload box.
What each claims over an upload
- jukeblocks.io, free toolRuns in your browser: nothing is uploaded to a server, and no project files are stored without explicit permission.
- jukeblocks.io, paid RecreateProcessed server-side; the terms are silent on training.
- songscription.aiPosting content grants a worldwide, irrevocable, royalty-free licence with the right to sublicense, expressly including training the company's AI models.
- ai-midi.com, webA separate Training Data Use Agreement is required; under it the company may anonymize inputs and outputs and use them to train and improve models.
- ai-midi.com, APIThe same terms state the opposite here: audio and generated files are not used for training and are deleted within 24 hours.
The same vendor, two answers
The training agreement states on its first page that it does not apply to the API, so the two entry points give your audio different lifetimes.
On the web path a training copy may be made after a successful conversion. A copy awaiting anonymization is kept only until anonymization completes, never longer than 30 days. Copies already anonymized and folded into a training dataset before withdrawal may continue to be used, and the company does not guarantee removing the data's influence from an already trained model.
If your audio is what you care about, that vendor's API is the shorter-lived path.
The five sources
| Source | What you rely on | What the terms do |
|---|---|---|
| Your own recording | You are the performer and, if you wrote it, the rights holder. | Nothing changes; a browser-local tool receives no copy. |
| A track you bought or licensed | The receipt and the licence's scope. | songscription's licence is personal and non-commercial. |
| A stream from a subscription service | That service's terms, which govern playback. | None of the three addresses it. |
| Audio from a video platform | songscription mentions this route only as audio you have the right to use. | ai-midi prohibits infringing third-party rights. |
| Someone else's stems | Their written permission. | ai-midi names copyright, neighbouring and voice-related rights. |
Read from the three sites' own documents on 2026-09-26; a reading, not legal advice.
What to keep
Each converter asks you to warrant that you hold the rights. So keep: for a bought track, the receipt and licence; for a stream, the subscription terms; for a video-platform rip, the platform's terms; for someone else's stems, their written permission. Your own recording needs nothing.
The two output positions
songscription's licence is personal and non-commercial, and forbids using a credit to obtain an output for sale or redistribution; the same terms forbid using any output to train a model. ai-midi takes the other position: all use of outputs, including commercial use, rests with the user, and so does the responsibility.