BPM TechnoFree · Offline · BPM tools for DJs

Local files stay on your device

Choose a supported audio file from your device to analyze it without uploading the track. The file is decoded in application memory and is not sent to BPM Techno.

MP3, WAV, M4A, AAC, and FLAC availability depends on the codecs supported by your browser or operating system.

A remote URL must point directly to audio

Use a direct link to a file that the browser can decode, rather than a streaming service page or a download page containing HTML. The sample link in the form demonstrates the expected format.

MP3 and WAV are commonly supported, but the exact codecs available depend on the browser and operating system.

Why some remote files cannot be fetched

Browsers enforce Cross-Origin Resource Sharing, usually called CORS. The server hosting the audio must allow bpmtech.no to read the response. A file can play in a browser tab and still reject programmatic access if its CORS headers do not permit it.

If a remote host blocks the request, use a file hosted with suitable CORS headers or the included sample. BPM Techno cannot bypass the remote server policy.

Accuracy and useful sections

• Use a full-quality file when possible; severe compression can soften rhythmic transients.
• Tracks with a stable electronic beat are generally easier than live performances with tempo drift.
• A detected value may represent half-time or double-time.
• Silence, ambient intros, and beatless material reduce confidence.

How the audio is handled

The URL is fetched directly by your browser. The decoded audio is analyzed in browser memory and is not uploaded to the BPM Techno feedback API.

Submitting the optional accuracy feedback sends the detected BPM, the analysis mode, and whether you marked the result correct. It does not send the audio file.