What You're Actually Looking At
Most people who stumble onto set list documentation for Phish do so because they attended a show, heard about it online, and then tried to figure out what was actually played. The band has been performing since 1983. That means roughly 2,900 concerts with anywhere from three to five songs per night, sometimes more, sometimes with extended jam segments that shift entirely from show to show. Keeping track of all of this by hand is not realistic. The reference works that exist fill that gap. I started cross-referencing Phish concerts about eight years ago after a friend sent me a recording of the December 31, 1995 show and told me to look up what Trey played during the "You Enjoy Myself" section. I found the set list on a forum, noticed the song names didn't always match the official titles, and spent the next three weekends building a spreadsheet that tracked alias names, improv tags, and segues. That was before I knew about the major compiled references. Once I did, my spreadsheet became a supplement, not a replacement.
The Phish Set List Bible Decoding The Bands Relentless Concert Machine
When people reference "The Phish Set List Bible," they are usually talking about one of two things. The original concept refers to compiled set list collections that attempt to document every official concert the band has played. These collections typically include the date, venue, opening song, closing song, and the full sequence of tracks in order. Some include encore information. Some include notes about segues or thematic groupings. The more thorough versions include improvisation highlights and notable jam transcriptions. The second meaning is more practical. It refers to the ongoing community effort by fans to maintain accurate, searchable databases of every Phish concert. These databases are maintained by volunteers who attend shows, compare multiple audience recordings, cross-reference official sources, and update entries when discrepancies appear. The work is continuous because Phish plays almost every night during their touring seasons, and new recordings surface constantly. Here is how you actually use these resources effectively. Start with the database or compiled list for the specific date you are researching. Match the date against multiple sources if possible. The major set list sites and the Phish.net database are the most commonly used. If a song appears in one source but not another, check the timestamp on any available recording. The discrepancy is usually a segue name, an improvised title, or a song that was started but abandoned mid-performance.
I ran into a specific issue last year that took me about four hours to resolve. A fan-submitted set list for a July 2013 show at Red Rocks listed "Mike's Song" as the second set closer. The official recording I had confirmed the song was played, but the outro sequence included material that didn't match the standard recorded version. The database entry showed the song, but the segue chain between "Mistaken Universe" and the reprise was documented differently across three different sources. What I ended up doing was pulling the actual soundboard recording, timing each transition, and matching it against the Phish.net thread where multiple attendees had posted their personal set lists. The correct sequence was only verifiable by comparing at least four independent audience recordings. I then updated my own tracking document with the verified sequence and noted the discrepancy sources for future reference.
Get the Full Details
How the Documentation Actually Works
The compilation process relies on several input types. Official venue records provide basic date and location data. Audience recordings from multiple seats in the hall allow cross-verification of set list content. Sometimes official band sources or promotional materials confirm song selections. Fan forums serve as the primary discussion and correction channel, where errors get caught within hours or days of a show. The most reliable entries come from shows with multiple high-quality audience recordings available for comparison. When only one source exists, the entry carries lower confidence and is usually flagged. Seasoned researchers check the confidence rating before citing any single entry, especially for older shows before the band's recording archival practices became more systematic. Song naming conventions add another layer of complexity. Phish songs often have multiple names depending on the era, the specific performance, and which section of the improvisation is being referenced. "You Enjoy Myself" might be listed under its standard title or tagged with a specific jam segment name like "YEM Jam" or "Blue Room YEM." "Tweezer" has dozens of documented variations. The databases attempt to normalize these into consistent entries, but normalization is not always perfect. You will occasionally see the same performance listed under slightly different song titles across different sources.
Common Mistakes People Make
The first mistake is assuming a single set list source is authoritative. No single source is complete or always correct. The second mistake is treating every listed song as a fully performed track. Phish frequently plays partial songs, segues into other material, or abandons songs mid-section. These fragments are sometimes listed in detailed databases but rarely appear on official releases. If you are building your own reference, mark these incomplete performances separately. A third mistake involves ignoring date ranges when searching. Phish has repeated the same set list structure on multiple tours. The March 1998 version of a particular show template is not the same as the August 2003 version, even though the song names match. The jam content, tempo, and duration can differ significantly. Always anchor your research to a specific date and venue, not just a song sequence. There is also a tendency to over-index on the most famous performances. The December 31, 1995 show gets cited constantly. The July 1997 Lake Bandshell run gets cited constantly. The vast majority of Phish concerts are not headline-making events. They are still worth documenting because they represent the baseline of the band's output. Ignoring the non-highlight shows creates a skewed understanding of how the band actually structures their performances night to night.
Where to Find the Resources
The primary hub for Phish set list documentation is Phish.net. The community there maintains the most comprehensive concert database available, with entries for virtually every show since the early 1980s. The site includes set lists, audience recording availability, forum discussions, and a wiki section covering song histories and performance notes. For compiled reference material in book form, the closest equivalent to a "Bible" would be the various fan-published set list compilations that circulate within the community. These are not officially published through major book distributors. They tend to be PDF downloads or print-on-demand collections maintained by dedicated archivists. Search terms like "Phish set list archive" or "Phish concert database PDF" will surface these resources. The quality varies considerably between authors. Some entries are meticulously researched with multiple source citations. Others contain unverified information copied from early forum posts without cross-checking. Discord servers and specialized Phish forums also host active set list researchers who share raw data files and spreadsheets. Joining one of these communities gives you access to people who are actively updating entries and can answer specific questions about individual shows. The Phish.net Discord is one option. Several smaller community servers exist as well.
Limitations You Should Accept
These resources will never be perfectly complete. Shows from the early 1980s have sparse documentation because the fan recording culture was in its infancy and many audiences were not preserved. Set lists for some 1990s shows have gaps where audience recordings have not been catalogued. The band's own official archive has been slowly releasing archival recordings, but the release schedule is slow and uneven. Even the best databases contain errors. Fan-submitted entries are human-generated. Typos happen. Songs get misidentified. Segue chains get reconstructed incorrectly. The community correction process catches most of these within days, but not all of them. If you are using set list data for serious research, verify critical entries against audio recordings whenever possible. The documentation also reflects whatever the community considers noteworthy. Quiet, straightforward shows with minimal improvisation are less likely to generate detailed discussion threads. This means the most thoroughly documented shows are often the most exploratory ones, which reinforces the skew I mentioned earlier. The average Phish show is underrepresented in the detail available online.
If your goal is simply to look up what was played on a specific date, Phish.net will handle that efficiently. If your goal is to study the band's structural patterns across hundreds of shows, you will need to build your own dataset by exporting and cross-referencing database entries. That process takes time but produces results that no pre-packaged reference can match.
