MI
SOFTWARE

Mixxx

Mixxx 2.5.6 is a free, open-source DJ application for Windows, macOS and Linux, with decks, beat analysis, headphone cueing, controller mapping, effects, recording and local library management.

Version 2.5.6Windows 10 1809+macOS 11+LinuxGPL-2.0-or-later

What Mixxx does

Mixxx is a real-time DJ application for two or more decks, beat analysis, headphone cueing, controller mapping, timecode vinyl, effects, recording, streaming and local music-library management. It is designed around live playback and transitions rather than multitrack editing or mastering.

Version and platform boundaries

Version 2.5.6 is the stable 2.5 release for Windows 10 build 1809 or later, macOS 11 or later and several Linux packaging formats. The 2.6 beta and 2.7 alpha lines are testing builds; keep a stable copy for performances and back up the library before opening it in a test build.

Audio routing and hardware

Headphone cueing normally needs two independent output paths. Controller support also depends on mappings, firmware, audio drivers and the operating system. Start with a low-volume test and verify main output, headphones, buffer size, clipping and device reconnect behavior before connecting a live system.

Library migration and recovery

The database stores paths, cue points, beat grids, playlists and history, but it does not replace the audio files themselves. Back up audio, the database, controller mappings and custom scripts together. Migrate a copy first, relink paths and sample several tracks before replacing a working setup.

Maintenance note

Review date: 2026-08-23. The page was checked against Mixxx 2.5.6, stable and test branches, audio routing, controller mappings, library migration and GPL licensing.

SAVE TO CLOUD

Save to your cloud drive

Open the cloud drive to get the file directly, or save it for convenient access on another device.

Links checked 2026-08-06
Save first, access when you need itOn desktop, scan with the matching cloud-drive app. On mobile, tap the save button.
GUIDE

Mixxx 2.5.6 installation, audio routing and first mix guide

Start with the stable build and a recoverable test library, configure main and headphone outputs, analyze a few tracks and rehearse recording before using the setup in a live environment.

Before you start

  • Use Windows 10 build 1809 or later, macOS 11 or later or a supported Linux package, and keep a stable copy of the music library.
  • Prepare disposable test tracks and low-volume monitoring. Headphone cueing needs a controller or audio interface with independent output channels.
  • Back up the database, playlists, cue points, controller mappings and settings before upgrading, changing package formats or testing a preview build.
01

Installation steps

  1. 01

    Install the stable 2.5.6 package

    Choose the package for the current platform and add only a small test music directory on the first launch. Do not open the only performance database in a preview build.

  2. 02

    Configure audio output

    Set sample rate, buffer, main output and headphone channels, then test left and right channels, latency, clipping and reconnect behavior at low volume.

  3. 03

    Add and back up the library

    Import a few tracks, analyze BPM, key, waveform and beat grid, close the application and copy the settings directory. Verify that the database and mappings are in the backup.

02

Quick start

  1. 01

    Prepare two decks

    Load clear test tracks, set cue points and gain, preview the next track through headphones and keep unverified signals away from the main output.

  2. 02

    Align beats and transition

    Check the automatic beat grid before using sync, then practice EQ, volume-fader and crossfader transitions. Correct a grid manually when BPM detection is wrong.

  3. 03

    Record and review a rehearsal

    Record a ten-minute practice, check clipping, level jumps, silence and latency, then save the history and playlist before rehearsing the same hardware connection.

Usage tips

  • Version 2.5.6 is the final maintenance release in the 2.5 line, while 2.6 beta and 2.7 alpha are for testing rather than an unattended live upgrade.
  • Custom MIDI and HID mappings can include scripts. Review their source and keep a known-good mapping backup before importing third-party files.
  • Moving from a system package to Flatpak can change the settings directory and require new permission for external music folders. Relink before deleting the old setup.
  • Recording or streaming music can involve copyright, performance and platform rules. The application's capability does not grant permission to redistribute a track.
Troubleshooting and uninstall

Why do the headphones and main output play the same signal?

Assign main and headphone outputs to different physical channels and check controller sound-card mode, cue buttons and the headphone mix control. A single stereo output usually cannot provide independent previewing.

Why is sync off-beat or a cue point shifted?

Zoom into the waveform, check the first beat, BPM doubling and variable-tempo sections, then adjust the grid and cue point manually. Migration between decoders or systems can require a spot check.

  1. Back up the library and mappingsCopy the settings directory, audio-library structure, playlists, history, broadcast settings and controller mappings, then sample the backup in the same stable version.
  2. Remove the application and optional dataUninstall the package or application. Only remove caches and settings after confirming they are no longer needed; music files normally live in a separate directory.
FAQ

Frequently asked questions

Does Mixxx have a paid Pro edition?

Mixxx 2.5.6 is a complete GPL open-source release and does not require a feature-unlocking subscription. Controllers, audio interfaces and external services can have their own costs and licenses.

Can I learn Mixxx with only a keyboard and mouse?

Yes for importing, playback, synchronization, EQ, crossfading and basic recording. Independent headphone preview normally requires an audio interface or controller with separate outputs.

Are the 2.6 beta and 2.7 alpha suitable for a live performance?

Keep the stable 2.5.6 build for live work. Preview builds can change databases and settings or expose regressions, so test them only with a complete backup.