Serato DJ Pro MIDI Mapping: Complete Guide.

Serato DJ Pro has MIDI mapping, and it works well. The problem is that its design has two preliminary steps people skip, plus a list of things that cannot be remapped that is not where you expect to find it.

This guide covers the complete official procedure and, above all, its boundaries: what you can change and what you cannot. That second part saves more time than the first.

What MIDI Mapping Allows in Serato

The feature lets you move frequently used controls in Serato DJ Pro to three different destinations:

• Your primary Serato hardware (the equipment that activates the program).
• A secondary MIDI controller connected alongside it.
• An official Serato accessory.

You can create, save and customise your mapping. One important consequence: assigning a function to a new control removes that function’s default assignment.

Preliminary Step: The Permission Almost Nobody Enables

If your primary hardware does not appear or will not allow mapping, this is almost always why.

Your primary hardware appears in the MIDI devices list on the MIDI tab, provided it has MIDI capabilities. If it does not appear, the documentation is clear about the likely causes: it has no available MIDI controls, cannot be remapped, or is simply disconnected or not recognised by the computer.

The permission is called “Allow Serato Hardware Remapping”, and you must enable it per device in the MIDI devices list. Only once it is enabled does the MIDI button on Serato DJ Pro’s main screen become available.

That answers a frequently asked question: the MIDI assignment button looks grey if none of these three conditions is met:

1. A secondary MIDI controller is connected.
2. Allow Serato Hardware Remapping is enabled for the primary hardware.
3. An official Serato accessory is connected.

In case 1 or 3, you do not need to change the permission. To remap your primary hardware, you do.

Assign a Control, Step by Step

1. Enable the permission for your primary hardware (if that is what you want to remap), then close SETUP.
2. Press the MIDI button at the upper left of the main window. This enables assignment mode and opens the panel.
3. Click the Serato function you want to map.
4. Operate your hardware’s physical control (press, turn or move it).
5. Check the assignment box: it changes from grey to blue once the assignment succeeds.

A warning that prevents surprises: assigning a new function to a control erases that control’s default function. It is not an error; that is how it works.

Two Assignment Directions

Serato allows both, which is one of its strengths:

Several Functions on the Same Control

You can assign several functions to a single button, knob or fader. If the control already has an assignment, Serato asks you to choose:

• O → Overwrite. Overwrites ALL previous assignments on that control.
• A → Add Additional. Adds an extra assignment while retaining previous ones.

The distinction matters: O does not erase only the most recent assignment; it erases all of them.

Several Controls for the Same Function

It also works the other way round: several controls (buttons) can target the same Serato function. The official method:

1. Hold Shift and click a function that already has an assignment.
2. Move or press another physical control on your MIDI device.

The new control is assigned and the original assignment stays. Both appear in the mapping panel.

Save the Preset BEFORE Starting (The Costliest Mistake)

This warning ruins afternoons of work, and the documentation spells it out.

You can create, save, delete and load MIDI templates on SETUP’s MIDI tab. But:

Make sure to create a new preset BEFORE starting to map, so you have a preset to save into when finished. Simply pressing “new” erases your current MIDI configuration.

In other words, create the preset first and map afterwards. If you map first and then create the preset, you lose your work.

A second warning follows the same principle: unsaved assignments are lost when you close the program.

Dial to Dial, Button to Button

One restriction surprises people coming from other programs:

Serato DJ Pro dials and faders must be assigned to dials or faders on the MIDI controller. Assigning dials and faders to buttons will not work, because the received MIDI signal is different.

The official recommendation is logical: button to button, knob to knob, fader to fader.

There is a clear technical explanation, applicable to any software: they are different message types. A continuous control travels as Control Change with a value from 0 to 127; a button or pad travels as a note message. They are not interchangeable, and the software cannot guess your intention.

If you have ever tried to map a fader to something and nothing happened, now you know why.

What CANNOT Be Remapped in Serato

This is the part missing from quick tutorials, and it determines which projects are feasible.

The official documentation explicitly excludes:

• Jog wheels and platters
• Input switches
• Shift buttons
• Performance pad mode buttons

It also lists official accessories that cannot be remapped at all: the Pioneer CDJ series, Roland TR devices and Numark Dashboard.

Pause over those two lists, because they change common conclusions:

• Jog wheels cannot be remapped. This fits what you already know about MIDI: a fast-turning control needs resolution the protocol does not provide. Here it is the manufacturer’s decision, rather than a limitation of your mapping.
• Pad mode buttons cannot be remapped. That means creating custom pad modes like rekordbox allows through Pad Editor is not an available route in Serato: mapping is closed off for precisely that element.
• Shift buttons cannot be remapped. So you cannot build your own SHIFT layer on the primary hardware from here.

If you came looking for a way to add Stems to your Serato pads, the honest answer is: through mapping, no. What the documentation does say is that you can move frequently used functions to a secondary controller or official accessory, and that is where real scope remains.

Undo a Mapping: Three Levels

Serato offers three ways to revert, and they need distinguishing because they do different things:

1. Revert one particular mapping. Click the mapped control and press ENTER while the blue box is visible. Only that mapping is reverted.
2. Disable the permission. Clearing Allow Serato Hardware Remapping on the MIDI tab keeps your XML loaded but disables custom mappings on your primary hardware. Useful when you want to retain secondary-controller or accessory mappings.
3. Restore Defaults. Prompts you to save your mappings and unloads the current XML, giving you a clean starting point. Important: it erases mappings for every device saved in that XML. If two devices are connected, both return to their default mappings.

Because point 3 is destructive, the documentation itself recommends backing up third-party mappings before changing the primary hardware.

Limitations to Know Before Mapping

Two more that are not obvious:

• Mappings are remembered even when you change hardware, but they may not fit. A preset for each different setup is recommended; otherwise mappings may not work correctly on each device.
• Remapping a pad in Hot Cue mode also remaps it in Saved Flip mode, and vice versa. They are not independent, and without knowing this, it can seem as though the program does strange things on its own.

Common Mistakes

• Failing to enable Allow Serato Hardware Remapping and concluding that your hardware cannot be mapped.
• Creating the preset after mapping. Pressing “new” erases the current configuration.
• Closing the program without saving. Unsaved assignments are lost.
• Assigning a fader or dial to a button. It does not work because of the MIDI message type.
• Pressing O assuming it overwrites only the most recent assignment. It overwrites them all.
• Using Restore Defaults with two devices connected. Returns both to factory defaults.
• Looking for ways to remap jog wheels, Shift or pad modes. They are excluded from official mapping.
• Expecting to put Stems on pads through mapping. Pad mode buttons cannot be remapped.

Next Step

You now have Serato covered, including its boundaries. This closes the round of ecosystem-specific mappings opened in this block: rekordbox, Traktor, Mixxx and Serato, each with its own model. The natural next step is the topic that should attract the most long-tail traffic in the whole cluster and has already appeared in all four guides: parameter jumps and soft-takeover, where these tools behave differently and where most people get stuck.