Song request apps for DJs compared (2026): what actually differs

Most song request apps have converged on the same surface: a QR code near the booth, a web page with no install, a list on the DJ's phone. What still differs is underneath — whether the guest is charged before the DJ has decided, whether the DJ can answer, and whether you pay a subscription or a percentage. This compares those three things, including where REQ loses.

A warning about this page before anything else: REQ makes one of these products. So does almost every other comparison you will find on this subject — the two most visible "honest comparisons" of song request apps in 2026 are published by song request apps. That is not a reason to dismiss them or this one. It is a reason to check whether a comparison names the case where its own product is the wrong choice. This one does, in the last section.

The surface is the same everywhere. Stop comparing it.

Every platform worth naming has the same guest experience, and it is the right one. A QR code sits near the booth. Someone points a camera at it. A web page opens in their browser. They pick a track and send it. Nothing to install, no account to create, no password at 1am in a dark room.

Rekwest states guests do not need to download the app or create an account. Lime DJ states everything runs in the browser with no app downloads required. REQ's request page asks for a track and, optionally, a first name. The category settled this argument years ago, because requiring a download at 1am destroys conversion and everyone found that out the hard way.

So a feature table that lists "QR code" and "no app required" as differentiators is padding. Three things actually differ.

Difference one: when the card is charged

This is the largest practical difference between these products, and it is almost never on a pricing page.

Tip-based platforms take the money immediately. A tip is not conditional on anything — that is what makes it a tip. NoSongRequests, Lime DJ and Rekwest all frame the payment as a tip or donation attached to a request. The guest sends it, it is gone, and whether the DJ plays the track is a separate question. If the DJ does not play it, the guest has paid for nothing and their recourse is to ask for a refund.

Hold-based platforms do not. The amount is authorized on the card — reserved, but not moved. Stripe documents this as placing a hold and uses hotel bookings as its own example: authorize on arrival, capture at check-out. The money only leaves the account if the DJ accepts. DJFY states guests pay only if the DJ accepts and plays the song within 30 minutes. REQ works on the same mechanism.

The difference shows up in refusals, and DJs refuse a lot.

There is no refund on a hold-based platform because there was never a payment to reverse. That is not a marketing distinction — it is a different object in the payment processor, and it is why the guest sees a pending line vanish instead of money leaving and coming back a week later.

One nuance in the other direction: a hold is not free of consequence for the guest. The amount is unavailable on their card until it releases. On REQ the window is 30 minutes; Stripe holds otherwise persist for around seven days before releasing on their own.

Difference two: whether the DJ can answer

On most platforms the flow only goes up. The request arrives, the DJ accepts it or ignores it, and the person who paid finds out by hearing the track or not hearing it. There is no acknowledgement, which is why people come back to the booth to ask again — the silence, not the refusal, is what makes them insist.

Some platforms add signals in the other direction, but between guests rather than from the DJ. NoSongRequests lets the audience see, like and upvote each other's requests, which turns the queue into a small social feed and gives the DJ a reason to play something. It is the crowd talking to itself.

Lime DJ goes further in a direction worth naming plainly: tipped songs are automatically bumped up the queue. That is a clear and defensible product decision, and it is pay-to-play — the amount changes the running order without the DJ deciding anything.

REQ is built on the opposite principle. The amount never changes the order, and the DJ's answer goes back down: a phrase they wrote before the set, sent in one tap, appearing on the page still open in the guest's hand. The DJ can also play the track and cancel the hold, so the person is charged nothing and their screen says so.

Difference three: subscription or percentage

Two models, and the arithmetic is worth doing before you pick.

Where REQ loses: 20% of $25 is $5, so above roughly $25 collected in a month the subscription model is cheaper, and the gap grows with volume. A DJ collecting $200 in a month pays about $40 on REQ against about $12 on NoSongRequests. If you are a busy resident collecting steadily every week, that is a real and growing difference, and no amount of product argument makes it go away.

Where REQ wins: there is no bill on a quiet month, no plan to choose, no feature locked behind a tier, and no decision to make before you know whether requests work for your room at all. On NoSongRequests' free tier, tipping is disabled — so the free plan cannot do the thing most DJs are trying. REQ's free tier is the whole product.

Both are defensible. They suit different people, which is the honest answer.

Difference four, arguably: how much product there is

This one is a preference, not a ranking, but it decides more than the price does.

Lime DJ bundles song requests with tipping, photo albums, live slideshows, music bingo and song voting. NoSongRequests adds shoutouts, booking enquiries, a searchable performer page, BPM, key, energy and lyrics on each request, and export to Serato, Virtual DJ, Rekordbox and Traktor.

That is a lot, and for a wedding or corporate DJ who is also running the room's entertainment, it is exactly right. One tool, one QR code, everything the night needs.

For a club or bar resident it is the wrong shape. The screen you look at for two seconds between two mixes should have one job. REQ does one thing: a request arrives, you play it, pass it, or cover it yourself, and you answer. There is no settings tree, no event mode, no second product to configure. Whether that is minimalism or missing features depends entirely on what your night looks like.

About "Serato integration"

Every platform that advertises DJ software integration means the same thing, and it is worth knowing what.

Serato publishes no API and no plugin SDK. Nothing third-party can display inside its interface — not a request, not a queue, not a notification. What the integration actually is: an export. NoSongRequests states you can export the song requests to your favourite DJ software, which produces a file the DJ imports.

That is genuinely useful before a set, to build a crate from advance requests, and after one, to review what was asked. It does not help mid-set, because a crate added while Serato is running does not appear until the library is rescanned or the software is restarted, and nobody restarts their DJ software at 1am.

If a platform's Serato integration is the reason you are choosing it, check whether it does anything during the only three hours that matter.

Which one, for whom

A wedding or private-event DJ running the room's entertainment: Lime DJ or NoSongRequests. The bundled features — photo albums, slideshows, shoutouts, booking enquiries — are the point, not padding, and a night with fifty guests will not trouble a free tier's limits.

A busy club resident collecting steadily every week: NoSongRequests Pro. At consistent volume, $5 a month beats any percentage, and the arithmetic is not close.

A DJ who declines most requests — because the room has a sound and most requests do not fit it: a hold-based platform, REQ or DJFY. On tip-based platforms every refusal creates a refund to process and a guest who paid for nothing.

A DJ starting out, or testing whether requests work in their room: REQ. There is no subscription to justify before you know, and the free tier is the entire product rather than a trial with the money turned off.

A DJ who wants the refusal to stop being a confrontation: REQ. This is the case the reply feature exists for, and no other platform sends the DJ's own words back to the person waiting.