SpotiQueue questions, answered properly

Can guests queue without a Spotify account?

Yes. Guests need a phone browser and your queue link or QR code, nothing else. They search on the SpotiQueue page or paste a Spotify track URL, and the search itself runs against Spotify on the server side. They never log into Spotify at all. You are the only person who connects Premium, and you do that once on the dashboard.

You can optionally turn on Require username so requests show a name in admin, or Require Google sign-in for identity that follows a guest across devices. Neither one is a Spotify login. Rooms with a mix of Android and iPhone work because everybody lands on the same web page, and guests who use Apple Music or nothing at all can still request tracks as long as they can find them through search or a shared link.

SpotiQueue adds approved songs to your Spotify queue. It does not play audio on guest phones and never asks them to install the Spotify app. Playback always happens on your connected Spotify session, whether that is a phone, a laptop, or a smart speaker you paired before the party started. You stay the DJ, and guests stay guests.

What happens if no one moderates the queue?

With Require approval (prequeue) off, valid requests go straight into your Spotify queue in order, and nobody has to sit watching the admin panel. You can still reorder, remove pending rows, or skip from the Live queue tab when a song lands wrong.

With prequeue on, walking away has a cost: requests pile up unapproved in the Prequeue tab and never reach Spotify until someone taps Approve. Guests at least see a submitted message rather than silence, so they know they have not been forgotten. For a hands-off house party among people you trust, leave prequeue off and lean on Songs before cooldown plus optional Ban explicit songs instead. For a wedding or an office event, give one person the job of checking Prequeue every few minutes.

Either way, playback continues in Spotify whether admin is open or not, and cooldown enforcement runs on the server, so one guest cannot flood the queue just because you stepped away to talk to people.

Can I ban a specific song for the whole night?

Yes. Open the Banned Tracks tab, paste in the Spotify track ID, and add a reason note for your own reference. Every future request for that ID is rejected with a clear not-allowed message, and the ban stays until you remove it from the list. On Pro you can ban straight from a pending row in Prequeue or Live queue, which adds the ID and clears the row in one step.

This is a different tool from Ban explicit songs in Configuration, which automatically blocks anything Spotify has flagged explicit at request time. Use both at a wedding when you want no explicit tracks at all plus a hard stop on the one joke song your cousin keeps submitting.

Bans apply per queue rather than globally across SpotiQueue. Blocking a device from Devices does something else again: it stops one phone from requesting anything, rather than stopping one song. If the same track reappears as a remix or a live version with a different ID, ban that ID too, or decline it in prequeue until the joke wears thin.

Does the big screen need its own device?

It needs a screen and a browser, not a separate SpotiQueue account or another Premium seat. Hosts commonly open /{slug}/bigscreen in a TV's built-in browser, on an old laptop over HDMI, on a mini PC tucked behind the monitor, or on a tablet propped up on a shelf. You can even run it on the same phone that hosts Spotify if you are desperate, though a dedicated screen looks better and keeps your phone free for admin.

The page shows now playing, the upcoming tracks, and the join QR code. It is read-only for guests, who still request from their own phones rather than from the TV, and the display device never needs a login. If your TV browser feels sluggish, a laptop on HDMI is usually smoother than fighting a smart TV web engine.

Pro adds Immersive mode and a lyrics delay setting. Free gets the same core now playing and QR layout. The page refreshes often enough for party use, and you are not maintaining a second app install on the television.

What's the difference between cooldown and prequeue?

Prequeue is a host approval step that happens before a song enters the queue. Cooldown is a per-guest rate limit that kicks in once someone has added, or tried to add, enough songs in a given window. They solve different problems and stack together cleanly.

Prequeue stops bad picks from ever reaching Spotify, because you decline them in the Prequeue tab. Cooldown stops one person flooding the queue with twenty requests in five minutes, even when every single one would have been approved. Run both, run one, or run neither.

Cooldown uses device fingerprinting by default through Track devices & enforce cooldown, while prequeue works from the Prequeue tab and its optional row actions. Declining a prequeue request still charges that guest's cooldown tally exactly like an approved add would, so spamming bad requests is not a way around the rate limit. Turning Enable queueing off pauses all new input without touching either system. Think of prequeue as taste control and cooldown as volume control over how fast one person can shape the room.

How many songs can a guest add before cooldown on Free?

You set Songs before cooldown anywhere from 1 to 3 on Free. The default is 1, which means the first successful chargeable request starts the Cooldown (seconds) clock, normally 300 seconds or five minutes unless you changed it in Configuration. Once the timer runs out they can request again, and the cycle repeats.

Pro lifts the cap on how high Songs before cooldown can go, so a patient crowd can queue more before waiting. The limit applies per guest device, and it follows a guest across devices when they signed in with Google or another provider. It is not a cap on the length of the party or on how many songs the room can play.

The exact row and the related limits live in the Free vs Pro comparison. Turning Track devices & enforce cooldown off removes fingerprint enforcement altogether, which most hosts of crowded rooms regret inside twenty minutes. Start strict on the first night and loosen Songs before cooldown once you have seen how the crowd behaves.

Does declining a request still trigger cooldown?

Yes. Prequeue declines count toward a guest's cooldown tally, the same as successful adds and other chargeable attempts. That closes the loophole where somebody spams offensive requests, assuming you will keep declining while they never hit a limit.

When a guest submits the wrong song by accident and you decline it, use Reset Cooldown on their device from the Devices tab so they are not penalized for a mis-tap. Hosts often tighten Songs before cooldown to 1 during the chaotic hours and loosen it to 2 or 3 later, and you can reset every cooldown at once when the night shifts from dinner to dancing.

Cooldown is about pacing rather than punishing people for their taste, so reset it whenever the house rules change mid-party. The guest page shows a countdown when someone hits the wall, which makes it obvious they are looking at a timer and not a personal block, unless you blocked their device as well.

Can guests undo a request they regret?

When undo is enabled in Configuration, guests can walk back their own recent adds up to the max songs back limit. On Free that depth is fixed at one song, and Pro lets you raise it for a longer walk-back window.

Undo only touches a guest's own recent requests. It does not reach the rest of the queue or anyone else's songs. It earns its place at office parties, where somebody realizes two seconds too late what they just added, and at dorm nights where mis-taps are constant. Hosts can still remove any pending row from Live queue regardless of what guest undo allows.

Undo does not refund cooldown that has already charged for the add; it removes the row as long as the song has not played. With Require approval (prequeue) on, undo applies to rows that actually made it into the live queue rather than items still sitting in Prequeue. Once a song starts playing, undo cannot rewind Spotify, so skip it from admin or Live queue instead.

Do I need to keep the admin panel open on my phone?

No. Guest requests, cooldown enforcement, and queue adds all happen on the server whether your admin tab is open or not. You can lock your phone and playback carries on in Spotify for as long as that session stays active.

Admin is only needed when you want to skip a song, approve prequeue rows, reorder pending items, change Configuration, or block a device. Plenty of hosts check Prequeue every few minutes rather than staring at the tab all night. There are no push notifications for new requests today, so plan on periodic glances or hand the admin phone to a co-host during peak hours.

Spotify disconnecting is a separate matter from admin being closed. SpotiQueue does not play audio; it only adds to your queue while Spotify is connected and your rules pass. Treat admin like a remote control you pick up when you need it, not something that has to stay awake on your screen all night.

What if my Spotify disconnects mid-party?

SpotiQueue needs an active Spotify session on your host account to add new tracks. If the connection drops, Spotify signs you out, or your Premium lapses, new guest requests may fail until you reconnect from the Spotify tab in admin or from the dashboard account panel.

Songs already sitting in the Spotify queue keep playing until that queue empties, so the room does not fall silent the moment something breaks. Reconnect when you can, and note that you never need to re-share the guest link or reprint QR codes to fix it. Test the connection before guests arrive, and keep the Spotify app in the foreground on the playback device if your operating system is aggressive about killing background apps. A quick reconnect beats debugging a login over loud music at 11 p.m.

Turning Enable queueing off is a gentler pause than disconnecting, and it needs no re-sharing when you reopen. If guests are seeing errors while you sort out the connection, switch queueing off temporarily so the page shows a clear disabled state instead of repeated failures.

Can I require Google sign-in but not Spotify?

Yes. Require Google sign-in is a guest gate in the sign-in section of Configuration. Guests sign in with Google once, and SpotiQueue ties that identity to their cooldown and block state across devices. Spotify stays host-only on the dashboard.

Pro adds optional Require GitHub sign-in and Require Discord sign-in for stricter identity if your crowd uses those services. Google is included on Free. If you would rather avoid sign-in entirely, Require username gives you names without any account, though a username is obviously easier to fake than a real account.

None of these options require guests to have or connect Spotify. Search still runs on the server against Spotify metadata, and guests never see a Spotify login screen. Guests who signed in may share one cooldown across their phone and laptop, which is what makes Track devices & enforce cooldown hold up in rooms where people switch devices mid-party.

Can I run SpotiQueue at a bar or club?

Not as licensed background music for a commercial venue open to the public. SpotiQueue runs on your personal Spotify Premium and is built for non-commercial parties: house nights, private hire events where you bring your own playback rights for that booking, staff parties, and pop-ups where you are legally DJing from your own account for one closed event.

Public bars and clubs need commercial music licensing and venue-grade systems designed for all-day playback. Using consumer Spotify in a commercial space breaks Spotify's terms whether or not SpotiQueue is involved. For a closed private function on your account with the venue's permission, see the private bar and function night guide, and if you are unsure, ask the venue what their license actually covers before pointing a queue link at paying customers all week.

SpotiQueue's moderation tools are not a substitute for a commercial license. Require approval (prequeue) and Ban explicit songs help you run a cleaner private night. They do not make consumer Spotify legal for daily trade.

How is this different from Spotify Jam?

Jam lives inside the Spotify app and works best when most of your guests already have Premium and will happily join a native session on their phones. SpotiQueue is a web link instead: no guest Spotify account, optional Require approval (prequeue), per-guest cooldowns, device blocks, permanent track bans, and a big-screen page laid out for a TV.

Jam means zero extra signup when your friend group already lives in Spotify and trusts each other with instant adds. SpotiQueue fits mixed phones, guests without Premium, entry by printed QR code, and hosts who want a real veto before the speaker changes. Jam has no equivalent of the Prequeue tab or the Banned Tracks list, and nothing like Songs before cooldown and Cooldown (seconds) for the night when one friend tries to queue fifteen songs in a row.

Both assume the host has Premium, and SpotiQueue never plays audio itself, it only adds to your queue. There is a longer Jam comparison with a full feature checklist.

Will explicit songs get through if I don't enable filters?

With Ban explicit songs off, tracks Spotify has flagged explicit can be requested like anything else, subject to your other rules such as prequeue or manual bans. Turning the toggle on blocks those adds at request time with a clear error, before the track reaches the queue or prequeue.

The filter reads Spotify's explicit flag on the track metadata rather than reflecting your personal taste. Edgy songs that Spotify has not flagged will still come through unless you decline them in prequeue or ban the ID by hand. Wedding and office hosts usually run the explicit filter and prequeue together so anything borderline still gets a human look.

You can enable the filter mid-party without restarting the link, and new requests follow the new rule immediately. Pair it with Banned Tracks for the specific songs that slip past the flag. The filter is the automatic half; prequeue is your judgment on everything Spotify still allows.

Can I pause guest requests without stopping playback?

Yes. Turn Enable queueing off in Configuration. Spotify keeps playing the current queue on your active device, and guests see that requests are disabled when they try to add something. Turn it back on when you want crowd input again.

It is genuinely useful during speeches, cake cutting, and first dance blocks, or when the pending list already runs two hours deep and you want to burn through what is there without new adds landing on top. Volume and skip still live in Spotify or the Live queue tab. Pausing this way is much softer than disconnecting Spotify, and it needs no re-sharing when you reopen.

Two details worth knowing. Prequeue rows already waiting still need your approve or decline, because switching queueing off only stops new submissions. Guests already on cooldown keep their timers too, and re-enabling queueing does not reset anything in Devices unless you reset cooldowns yourself.

What happens when the queue gets long?

SpotiQueue keeps accepting requests until you stop it with Enable queueing off, or until guests hit their own cooldowns. Songs play through Spotify in order at normal speed, because there is no turbo mode. You can reorder pending items in Live queue, remove the ones that will never suit the room, or disable queueing for a while so the list drains.

There is no hard cap on total queue length in the product. If the list looks absurd at 2 a.m., that is a host decision: trim pending rows, tighten Songs before cooldown, pause requests, or let it ride while people are still engaged. Multiplying average song length by the pending count gives you a rough answer for the guest who wants to know when their track is coming.

The up-next list on the big screen helps the room regulate itself without you narrating the backlog. A long queue means your cooldown is loose or your crowd is patient, not that anything has broken. Reorder Live queue when the mood moves so the next hour matches the room, even if the list looked fine an hour ago.

Can multiple people co-host moderation?

Today, one Spotify-connected owner account controls admin for a queue. There is no separate co-host login with split permissions on the same queue.

In practice, people pass the admin phone around, mirror the panel onto a laptop, or put one person on Prequeue while another works the room and handles skips. The dashboard owner can sign in on two devices with the same account if you trust both operators. Proper multi-moderator roles may arrive later, so for now plan on one owner account and informal handoffs.

For a large wedding, keep the moderator's phone quiet so incoming calls do not interrupt approvals mid-tab. Guest requests keep flowing on the server while the phone changes hands. Agree out loud who holds it during peak hours, so two people do not approve and decline the same row by accident, and remember the Devices tab still shows who requested what if you need to reconstruct the night afterwards.

Is there a song limit for the whole party?

There is no total cap on how many songs the room can queue across the night. The limits are per guest, through cooldown and optional prequeue pacing, rather than a global ceiling that stops the party at fifty tracks.

What Free does limit is how many queues you can own, which is one, and how high Songs before cooldown can go, which is three. Neither of those touches how many hours the playlist runs. Playback ends when you stop Spotify, clear the queue, or go home, not when SpotiQueue quietly hits a hidden maximum.

Spotify itself can rate-limit API calls under extreme load, but that is rare at party scale, and typical house and wedding crowds stay well inside normal use. A four-hour party where forty guests each add two songs is completely ordinary, and the product is built for exactly that on personal Premium. If you do want a hard stop, use Enable queueing off and trim pending rows in Live queue rather than hunting for a total cap that does not exist.