How SpotiQueue works, from setup to wind-down

Before anyone arrives

Sign up on the dashboard to create your SpotiQueue account, then connect Spotify Premium on the Spotify tab. SpotiQueue never plays audio itself. It adds approved tracks to your Spotify queue, and volume, pause, and skip stay in the Spotify app or on whatever speaker you already paired.

Next, create a queue from the dashboard and pick a display name for guests to see at the top of the request page. Free gives you a permanent random URL that never changes. Pro lets you add a custom queue URL on top of it, so your party name, wedding hashtag, or dorm floor label points at the same queue and makes for cleaner QR codes and printed signs.

Open instance admin before the first guest walks in. On the Spotify tab, check that playback is connected and that your active device is the speaker you actually plan to use. If Spotify is still pointed at your phone when the sound bar is what the room will hear, fix it now rather than after twenty requests have landed somewhere nobody can hear them.

Skim the rest of the admin tabs once so you know where Prequeue, Live queue, Devices, and Banned Tracks are. You do not need every toggle perfect on night one, but you should be able to skip a song and turn off new requests without searching for instructions at midnight. If you want to see the guest side before committing, the demo queue runs the same request flow without touching your Spotify.

Configuration defaults worth knowing

Open Configuration and read the defaults before changing anything. Most house parties run fine on them as they ship:

• Enable queueing is on, so guests can submit requests until you turn it off.
• Require approval (prequeue) is off, so valid requests go straight into the pending list and then into Spotify in order. Turn it on for weddings, office socials, or any room where you want a human yes or no before the speaker changes.
• Track devices & enforce cooldown is on. SpotiQueue fingerprints browsers so one guest cannot queue endlessly from the same phone.
• Songs before cooldown defaults to 1. Once a guest hits that many chargeable attempts, they wait out Cooldown (seconds), which defaults to 300, or five minutes.
• Ban explicit songs is off until you enable it. With it on, anything Spotify flags as explicit is rejected at request time with a clear error.
• Require username is off. Turn it on when you want requester names showing up in admin.
• Require Google sign-in is off. It gives you stronger guest identity across devices, and it is not a Spotify login.

Guests never need a Spotify account for any of this. You are the only person who needs Premium connected on the dashboard.

Getting the link out

Head to the QR Code tab in admin. From there you can copy the queue URL, download the QR image, or grab a shareable graphic for Instagram stories and printed signs. Text the link into the group chat, tape a QR code near the drinks, or let the big-screen view put the same code on the TV.

Guests open the page in any mobile browser. No install, no Spotify login on their end. They search for a track or paste a Spotify link and tap request. With Require username on, they enter a display name first. With Require Google sign-in on, they run through a quick sign-in once before the search box appears.

Test the link yourself on a second phone before anyone arrives. Search a song, submit it, and confirm it lands in Live queue and eventually plays on your active Spotify device. Those two minutes catch the three classic problems: the wrong speaker, a disconnected Spotify account, and Enable queueing left switched off.

Optional but worth doing: open /{your-slug}/bigscreen on a TV, a laptop on HDMI, or a cast browser tab. It shows what is playing, what is next, and the join QR code, which stops people asking you for the link every ten minutes. The big-screen page needs no login and no Premium seat of its own.

What the guest actually sees

The guest page is search-first. A guest types a song title or artist, picks from the results, and hits request. Where URL input is enabled they can paste an open.spotify.com track link instead. They get a confirmation when the add works, or an error if they are on cooldown, blocked, or banned, or if Enable queueing is off.

With prequeue off, a successful request means the song is queued for Spotify playback in order, subject to any reordering you do in Live queue. With Require approval (prequeue) on, they see a submitted-for-approval message and wait for you to act. Either way they can check now playing on the same page to see what made it through.

A guest who hits cooldown gets a countdown in seconds. That friction is deliberate, not a bug. They can still browse and watch the queue, they just cannot add again until the timer runs out or you tap Reset Cooldown for their device on the Devices tab.

Errors are written in plain language: rate limited, song banned, blocked by the explicit filter, device blocked, queueing disabled. Nobody gets dumped onto a Spotify login screen, because guests never needed Spotify in the first place.

The prequeue path

With Require approval (prequeue) on, a guest taps request and gets a submitted message rather than an instant add. The row appears in your Prequeue tab with the track name, the requester label, and Approve and Decline buttons. The tab polls every few seconds, so there is nothing to refresh by hand.

Approve pushes the track into the live queue and counts toward that guest's cooldown tally. Decline sends them away without adding the song, and the attempt still counts against their limit exactly like a successful add would. That is what stops somebody firing off twenty offensive requests through the approval window, hoping one slips past while you are looking the other way.

Pro adds one-tap Ban Track and Block actions to every prequeue row, so you never leave the tab. On Free you ban tracks from Banned Tracks and block devices from Devices instead. Either way, prequeue is the right mode for weddings, office parties, and any room where you want a quiet veto before the speaker changes.

If you are not going to watch admin all night, hand the job to one person who can glance at Prequeue every few minutes. Guests can tell the difference between a request that was received and one that was ignored, and it matters when the dance floor is loud and you are nowhere near your phone.

Live queue during the party

The Live queue tab mirrors what SpotiQueue is about to hand over to Spotify. Drag rows to reorder what is coming when the mood shifts, pull a pending item that will not suit the next hour, and skip the current track from admin without switching over to Spotify.

Clear upcoming removes SpotiQueue's pending songs from the list. It leaves alone anything sitting in your native Spotify queue that did not come through SpotiQueue. Worth knowing at 1 a.m., when someone insists a song they added in the Spotify app has vanished and you need to be sure which list you actually cleared.

Turn Enable queueing off in Configuration when you want playback to carry on but no new guest adds. That covers speeches, cake cutting, and the moment you realize the pending list already runs two hours long. Playback continues, and the guest page stops accepting requests with a clear message rather than failing silently.

You do not need admin open for guest requests to work. Cooldown enforcement and queue adds all happen on the server whether your tab is open or not. Admin is only for skipping, approving prequeue rows, reordering, changing Configuration, and blocking a device.

A cooldown worked example

Say Songs before cooldown is 2 and Cooldown (seconds) is 300. Guest A successfully queues two songs within a few minutes. Their third attempt comes back rate limited, and the guest page shows how many seconds are left before they can try again.

Three things charge against that allowance: successful adds, rejected requests that count as chargeable attempts, and prequeue declines. There is no way to game the approval queue into free attempts.

Guest B, who signed in with Google, may carry the same cooldown across their phone and laptop, because SpotiQueue can tie those sessions to one identity. That is what stops someone switching devices to get around Track devices & enforce cooldown. If a guest genuinely mis-tapped, use Reset Cooldown for that one device on Devices, or reset every cooldown at once when you change the house rules at midnight.

Free caps Songs before cooldown at 3, and Pro lifts the cap so you can allow more adds before the timer starts. You can switch Track devices & enforce cooldown off completely, though at a crowded party you will understand why fingerprinting exists within about twenty minutes. Full plan limits live on the Free vs Pro comparison.

Big screen

The big-screen route is public and needs no login. Open /{your-slug}/bigscreen on whatever screen the room already has. It pulls now playing and queue state the same way the guest page does, but laid out for a wall: large type, a join QR code, and the up-next list.

People scan instead of shouting "what was the link again?" across a loud kitchen, and because the display shares its queue state with guest phones, nobody argues about what is coming next. It is built for reading at a distance rather than in your hand.

All it needs is a screen and a browser, not a separate SpotiQueue account or Premium seat. Hosts run it on the TV's built-in browser, an old laptop on HDMI, a mini PC behind the monitor, or a tablet propped on a shelf. It is read-only for guests, who still request from their own phones rather than from the TV.

Pro adds Immersive mode, plus a lyrics delay setting for nudging synced lyrics into time under the album art. Free hosts get the same core now playing, up next, and QR layout.

Wind-down

As the party thins out you have a few gentle options. Leave cooldowns as they are and new adds slow down on their own. Drop Songs before cooldown to 1 if one person is still spamming. Or turn Enable queueing off so Spotify plays out the backlog while nobody adds anything new.

The Devices tab lists every fingerprint that has requested, with last seen, cooldown state, and block status. Sort and filter it when the room was big. A device's history shows its recent attempts, which is how you work out who kept queueing the same track.

Spotify keeps playing whether admin is open or not, so playback needs no babysitter. If Spotify disconnects mid-party, reconnect from the Spotify tab or the dashboard account panel; songs already sitting in the Spotify queue keep playing until that queue empties.

SpotiQueue is built for non-commercial parties on personal Premium: house nights, birthdays, dorm hangouts, and private hire events where you are legally running your own playlist for that booking. It is not licensed background music for a commercial venue open to the public. If you are unsure, read what the detailed FAQ says about commercial use before pointing a queue link at paying customers all week.

When you are finished for the night, stop playback in Spotify or let the queue drain. There is no need to delete the queue. The same link works next time, which is exactly why permanent Free URLs matter for a recurring friend group.