setlist.fm

setlist.fm asks you to enable JavaScript because the site uses a JavaScript-based check to confirm you are not a robot before letting you continue. If JavaScript is turned off in your browser, the page cannot run that verification, so it shows a "JavaScript is disabled" message instead of the content you came for. Enabling JavaScript and reloading the page is the direct fix.

What the message actually means

The notice on setlist.fm states that JavaScript is required to verify you are not a robot, and that you should enable JavaScript and then reload the page. This is a bot-protection step, not a sign that your account, browser, or the site itself is broken. The verification runs in your browser, so it needs JavaScript to execute.

How to enable JavaScript and get back in

The exact menu names differ by browser, but the path is similar everywhere:

1. Open your browser's settings (often under a menu labeled Settings, Preferences, or a three-dot/three-line icon).
2. Find the Privacy, Security, or Site settings section.
3. Locate the JavaScript control and set it to Allowed (or turn the block off).
4. Return to the setlist.fm tab and reload the page.

Expected result: the robot check runs, and the page content loads normally.

If JavaScript is already enabled

• Reload the page first — the check sometimes needs a fresh load.
• Check extensions: ad blockers, script blockers, and privacy extensions can block the verification script even when JavaScript is on globally. Try pausing them for setlist.fm.
• Try another browser or a private/incognito window to rule out a conflicting extension or cached state.
• Confirm you are not in a restricted mode that disables scripts by default.

Common sticking points

The short version

The JavaScript requirement is setlist.fm's way of running a robot check. Enable JavaScript in your browser settings, reload the page, and if it still fails, look at extensions and try a different browser or incognito window.

Setlists on setlist.fm are contributed by the site's user community rather than by an official editorial team or by the artists themselves. That means accuracy depends on how well each entry has been sourced and reviewed by other users, and you should treat any single setlist as a community claim rather than a verified record. The practical question is not "is this official?" but "how well-supported is this particular entry?"

How the contribution model works

setlist.fm is built around crowd-sourced concert data. In practice this means:

• Registered users submit setlists after a concert, listing the songs played and their order.
• Other users can edit existing setlists to correct song titles, fix the running order, add or remove songs, or fill in missing details.
• Concert metadata (venue, date, tour name, and similar fields) is also maintained through the same community editing process.
• Moderation happens socially, through other users reviewing, correcting, and sometimes disputing entries, rather than through a formal fact-checking desk.

Because of this, the same setlist can pass through many hands over time. A well-attended show by a popular artist often accumulates multiple edits and corrections, while an obscure show may sit with a single unverified submission.

What this means for reliability

The honest answer is that reliability varies by entry. A few conditions tend to make a setlist more trustworthy:

Conversely, a setlist with a single contributor, no supporting detail, and no subsequent edits is the weakest case. It may still be right, but nothing in the record confirms it.

How to judge a setlist before relying on it

If you want to use a setlist for something that matters — building a playlist, checking whether a song was played, or citing a tour's repertoire — work through these steps:

1. Open the specific setlist page and look at the edit history or contributor information if it is shown.
2. Cross-check against another source for the same date, such as a fan recording, a review, or a second setlist site.
3. Compare with adjacent dates on the same tour. Setlists usually follow a pattern, so an outlier deserves extra scrutiny.
4. Check the comments or notes attached to the entry, where users often flag uncertainty.
5. Treat the entry as provisional if none of the above gives you corroboration.

Common pitfalls

• Assuming "on setlist.fm" means "confirmed." It means "submitted by a user." Those are different claims.
• Trusting song order absolutely. Order is one of the most frequently corrected fields, since attendees often misremember sequencing.
• Ignoring covers and guests. Special guests, covers, and one-off performances are the entries most likely to be missing or wrong.
• Expecting the site to work without JavaScript. The site requires JavaScript to load; if it is disabled, you will be blocked by a verification step before you can view anything.

Bottom line

setlist.fm's setlists come from fans and other users, not from artists or an official authority. Use them as a strong starting point, especially for well-documented shows, but verify anything you depend on against a second source. The more consequential your use, the more you should treat a single entry as a lead rather than a fact.

setlist.fm is a crowd-sourced database of concert setlists, so the range of what you can find is broad: setlists from individual artists and bands, festival appearances, and shows across many genres and regions. You can typically look them up by artist, venue, date, or tour. The main limitation is coverage — a setlist is only there if someone has added it, and the site requires JavaScript to load, so you need a browser with JavaScript enabled to browse.

What the setlists cover

Because entries are contributed by users rather than generated automatically, the catalog reflects what fans have chosen to document. In practice that means you can expect to find:

• Artist and band setlists — the songs played at a specific concert, usually in performance order.
• Festival setlists — sets from multi-artist events, which are often shorter and may differ from a band's own headline shows.
• A wide spread of genres and regions — the database is not limited to one style or country, since contributors add shows from many scenes and locations.

Ways to search and filter

The site is organized around a few common dimensions, which is what makes it useful for looking up a specific show rather than browsing aimlessly:

Combining these lets you narrow down to a single concert, or compare how a setlist changed across a tour.

What a setlist entry can include

A typical entry goes beyond a bare song list. Depending on what the contributor recorded, you may see:

• Song order — the sequence as performed.
• Covers — songs by other artists played during the set.
• Improvised or special moments — for example, a jam, a guest appearance, or an unusual addition.

Not every entry is equally detailed; the level of information depends on the person who submitted it.

Practical things to know before you rely on it

• Coverage is uneven. Popular artists and well-documented tours tend to have more complete entries than obscure acts or one-off local shows.
• Accuracy depends on contributors. Treat entries as fan-reported rather than official, and cross-check if a detail matters.
• JavaScript is required. If the page shows a "JavaScript is disabled" message, enable JavaScript and reload before you can browse.

If you want to know who adds these setlists in the first place, that is covered separately in the question of who contributes setlists on setlist.fm.

setlist.fm is a music resource site built around concert and festival setlists — the lists of songs a band or artist actually performed at a given show. You use it to look up what was played at a specific concert, browse an artist's recent setlists, or contribute setlist information yourself. It falls into the broader category of music discovery and library/reference management rather than streaming: the site organizes performance data, it doesn't play the music for you.

What you can actually do on setlist.fm

The core value is a searchable, community-maintained database of live performances. Typical uses include:

• Checking a past show — find the date and venue, then read the exact songs and order played.
• Previewing an upcoming tour — look at recent setlists from the same tour to get a sense of the likely song pool.
• Browsing an artist's history — see how setlists change across tours, cities, and years.
• Adding or correcting a setlist — because the content is user-contributed, you can submit a setlist you attended or fix errors in an existing one.

How the site is structured

This structure is what makes it useful as a reference tool: you can navigate from a broad artist view down to a single night's performance.

A practical example

Suppose you want to know what a band played on the last night of a tour. You would:

1. Open the artist's page.
2. Sort or scan to the most recent date.
3. Open that setlist entry to read the songs in order, including any encore.

The expected result is a complete, dated record of that performance — useful if you're deciding whether to attend a future date, writing about a show, or just curious about a set you missed.

Things to keep in mind

• It's community-edited. Accuracy depends on contributors, so treat individual entries as best-effort records rather than official documents.
• JavaScript is required. The site needs JavaScript enabled to load; with it disabled, you'll hit a verification page instead of content.
• It's a reference, not a player. setlist.fm tells you what was played — it doesn't stream the songs.

If your goal is to find out what a specific artist played at a specific show, or to help document live performances, setlist.fm is the right kind of tool. If you want to actually listen to the music, you'll need a streaming service alongside it.