The Row That Proves You Were There
Scroll back far enough in your Concert Archives history and you will hit a show from 2019 that you know you went to, because it says so. Artist, venue, date, confirmed. All of it correct. And you cannot remember who drove, what they opened with, or why you still bring that night up at parties.
That gap is what sends people looking for an alternative. Not a broken tool. A different question.
Concert Archives answers "were you there," and it answers it at a scale nobody else has matched. If you have started wanting something that answers "what was being there like," that is a different kind of product. Here is the honest comparison, including the part where staying put is the right call.
What Concert Archives Gets Right
Start with the scale, because the scale is the achievement. Concert Archives holds over 1.7 million concerts, over 1.29 million bands, and over 645,000 venues. Those entries did not come from a licensing deal. Fans typed them in, one show at a time, and other fans checked them.
"The concert database for fans, by fans" is not marketing language layered over something else. It is an accurate description of how the thing was actually built, and anyone who has tried to run a crowd-contributed database at that size knows how hard it is to keep alive for years.
The feature set backs it up: personal concert history tracking, stats, favorites, bucket lists, upcoming concert discovery, group meetups, and concert anniversary reminders that surface a show you saw on this date a decade ago. There is a real community around it, where fans browse and engage with each other's histories.
If that community database is the part you love, that is a genuinely good reason to stay.
Two Different Questions
Here is the reframe, and it has nothing to do with anything being wrong.
A community database and a personal memory record are different products that happen to share a search term. They answer different questions.
"Were you there?" is a database question. Date, venue, artist, verified, slotted into a shared public record that thousands of other fans also use. It needs consistency, coverage, and contributors. Concert Archives is built to answer it, and it does.
"What was being there like?" is a memory question. Who came with you. What got played. What you wrote down the next morning while it was still loud in your head. The one song that stopped the room. That question needs a private place to put unstructured, personal, slightly embarrassing detail.
If something has felt missing, it is probably not a flaw in the tool you are using. It is that you were asking the second question of a product built to answer the first.
The Head-to-Head
Two products, two jobs. Here is the side-by-side, with their column written the way they would write it.
| Concert Archives | Concerts Remembered | |
|---|---|---|
| Built around | The world's concert history, maintained by fans | Your concert history, kept for you |
| Where the data comes from | Community-entered | You, with setlists synced from setlist.fm |
| The personal layer | Attendance, photos, stats | Written memories and notes, photos, ratings, who you went with, favorite song of the night |
| Sharing your history | Public profiles and an active community to browse | Private by default, with an optional clean public profile if you want to share |
| Festivals | Logged from the lineup | Mark the sets you actually saw |
| Year in review | Profile stats | Shareable recap cards for any period you pick: a year, several years, or all time |
| Moving your history in | Import tool reads the Concert Archives format directly |
The personal layer row is the one that matters most. Attendance plus photos plus stats is a complete answer to the database question. It is a list that proves you were at the show but cannot tell you who you went with. In Concerts Remembered, a show takes about 30 seconds to log (artist, venue, date), the setlist attaches on its own from setlist.fm data, and then the rest of the entry is yours: written memories and notes, photos, a star rating, the people who came with you, your favorite song of the night, and an experience checklist. That is the layer that makes a 2019 entry mean something ten years later instead of being a line you scroll past with no feeling attached to it anymore.
The sharing row is a genuine philosophical split, not a feature gap. Concert Archives is public by design, and that is the point: your profile is part of a shared record, and browsing other fans' histories is half the fun. Concerts Remembered is private by default. You can create a public profile if you want one, but nothing leaves your account unless you decide it should. Neither approach is better in the abstract. They serve different instincts.
Festivals split the same way. A lineup-based log tells you that you were at the festival. Festival Mode asks a narrower question: which sets did you actually stand in front of? If you skipped four acts to sit in the shade, your record should say so.
When Concert Archives Is the Right Choice
Some of you should close this tab and keep doing what you are doing.
If you love browsing the global database, if contributing entries that help other fans find their own shows feels good, if having a public profile inside an active community is part of why you log at all, if the discovery and meetup side is how you find your next show, stay. That is exactly what Concert Archives was built for and it does it well. Nobody needs to talk you out of a tool that is working.
Not every tool needs replacing. A lot of "alternative" searches end with the person realizing they already had what they wanted. That is a fine outcome, and it is a real one.
When Concerts Remembered Is the Right Choice
The case for switching is narrower and more specific.
You want the record to be yours. The written memory of the night, typed the next morning. The setlist already sitting there without you rebuilding it. The name of the friend who drove. The song that wrecked you at the second encore. Kept private unless you decide otherwise, which is the default, not a setting you have to hunt for.
You want festivals logged as what you actually saw, not what the poster promised.
And you want recaps that stretch. Shareable recap cards run across any period you pick: one year, a five-year stretch, or your entire history. If you have been going to shows since 2011, a single-year summary is a thin slice of the story. Being able to generate a recap card for the whole run is a different experience than seeing this year's count.
If you want the fuller tour of what that looks like in practice, the complete guide to the app walks through it.
Switching Takes Minutes, and You Keep Everything
Here is the part people assume will be painful.
Export your history from Concert Archives. Open the app's web import tool, paste it in, and it recognizes and parses the Concert Archives format directly into draft shows with artist, venue, date, and location already filled. You review the drafts, confirm them, and setlists attach automatically from setlist.fm data. Minutes, not an evening with a spreadsheet open.
Which means the important framing: your Concert Archives history is an asset, not sunk cost. Those years of logged attendance become the skeleton of the fuller record. The memory layer goes on top of shows you banked years ago. You can go back to a 2014 entry and add the three sentences you still remember, and now it is a memory instead of a row.
If you are rebuilding older shows from scratch, how to find your concert history and how to build your concert archive cover the ticket-stub and email-receipt archaeology.
Or Keep Both
This is not binary, and plenty of people run both.
Keep contributing to the community database if that matters to you. It helps other fans, and the database only stays good because people feed it. Keep the private memory record separately for yourself.
But if you only keep one, keep the one holding the memories. Attendance can be reconstructed later from tickets, emails, and setlist databases. Memories cannot. Nothing brings back what you were thinking during the third song if you never wrote it down.
FAQ
What is the best alternative to Concert Archives?
It depends on what you are missing. If you want a bigger or better community database, honestly, there is not much reason to leave: Concert Archives has over 1.7 million concerts and a fan base that keeps it current. If what you want is a private record of what each show was actually like (written memories, photos, ratings, who you went with, favorite song of the night, setlists attached automatically), that is a different category of product, and Concerts Remembered is built for it. Most people searching "concert archives alternative" are hitting a category mismatch, not a quality problem. Figure out which question you are asking first, and the answer gets obvious.
Can I export my Concert Archives history?
Yes. Concert Archives lets you export your logged concert history, which is one of the more respectable things about it: your data is not held hostage. Once you have the export, you can keep it as a personal backup, drop it into a spreadsheet, or paste it into the Concerts Remembered web import tool, which recognizes the Concert Archives format directly. Exporting does not delete anything on their side either, so you can move a copy without giving up your account or your contributions to the community database.
What is the difference between Concert Archives and Concerts Remembered?
Concert Archives is a community database. It answers "were you there?" with a verified, public, shared record built by fans across over 1.29 million bands and 645,000 venues. Concerts Remembered is a personal memory record. It answers "what was being there like?" with written memories, photos, star ratings, companions, favorite song of the night, and an experience checklist, all private by default. Different products, same search term. One is about the world's concert history. The other is about yours.
Can I import my Concert Archives data into Concerts Remembered?
Yes, and it is the fast path. The app's web import tool reads the Concert Archives export format directly. Export your history, paste it in, and it parses into draft shows with artist, venue, date, and location. You review the drafts, confirm, and setlists attach automatically from setlist.fm data. It takes minutes rather than a night of manual entry, and every show you already logged becomes a foundation you can add memories to later.
Is Concert Archives still worth using?
Yes, genuinely. It is one of the better fan-built projects on the internet: over 1.7 million concerts, maintained by the people who attended them, with bucket lists, stats, anniversary reminders, upcoming show discovery, and group meetups on top. If you like browsing other fans' histories, contributing entries that help strangers find their own shows, or having a public profile inside an active community, it does that well and nothing here should talk you out of it. The only reason to look elsewhere is if you want a private memory layer per show, which is a different job. Plenty of people use both and are perfectly happy.
What is the best app to track concerts you have been to?
The honest answer is that it depends on whether you want a list or a record. If you want a verified attendance list inside a shared database, a community platform serves you well. If you want each show to hold what actually happened (the memory you wrote the next morning, the photos, the rating, the friend who came, the setlist), you want a personal memory app. Concerts Remembered logs a show in about 30 seconds and attaches the setlist for you, so the friction is low enough that you actually keep doing it. There is a fuller breakdown in our roundup of the best concert apps.
Where do the setlists come from?
Setlist.fm. It is our integration partner, and setlist data syncs from there automatically when you log a show, so you do not type a single song title. If you have been marking "I was there" on setlist.fm for years, that history is also useful to you, and we wrote about what to do with your setlist.fm data.
Do I have to make my concert history public?
No. Concerts Remembered is private by default, and that is the whole posture: your memories are for you unless you decide otherwise. If you do want to share, you can create a public profile showing your concert history. It is opt-in, not opt-out. If you are currently tracking shows in a spreadsheet and weighing whether an app is worth it, this piece on tracking concerts without a spreadsheet covers the tradeoff.
Ready to put the memory layer on top of the years you already logged? Get Concerts Remembered for iOS or Android.
Share: