Packing for a conference is a different job from packing for a trip: the bag is smaller and everything that matters fits on one list. Forget socks and the hotel gift shop can help; forget the charger, the badge, or the business cards and the day gets harder at exactly the wrong moment. This conference packing list is a free printable two-page set built for that job. Page one is a bag table with 8 write-in item rows, each with a packed circle and a notes column. Page two covers the small stuff that carries the day: a badge and business cards box with 3 lines, a day-before box with 3 lines, and 4 opinion tips, each labeled as an opinion. If you want the event side of the same problem, the hackathon prep checklist covers prep through demo day, the hackathon calendar template tracks deadlines, and the web3 event calendar guide compares ways to pick what to attend.
How to use this page: print both pages at 100% scale. On page one, one row per item: write the item, circle Packed when it is in the bag, and use Notes for whatever the row waits on, like a charger that is currently charging the phone it charges, or a card that is still at the printer. Nothing on the table is pre-filled, because the items that matter depend on your bag, your role at the event, and your floor plan; write your own rows. On page two, the badge box holds the pocket where the badge and cards live, the day-before box holds the things that only work if they happen the night before, and the tips are opinions you are free to argue with.
Nothing on the sheets is pre-filled: the 8 rows, the 3 lines, and the 3 lines are empty on purpose. The same two pages work for a speaker, an exhibitor, or an attendee, because nothing on them assumes what you are bringing or what you are going for.
One row per item. Write the item, circle Packed when it is in the bag, and use Notes for whatever the row waits on: a person, a charger, a printout.
| Item (write it in) | Packed | Notes (write it in) |
|---|---|---|
| 1. ____________ | ||
| 2. ____________ | ||
| 3. ____________ | ||
| 4. ____________ | ||
| 5. ____________ | ||
| 6. ____________ | ||
| 7. ____________ | ||
| 8. ____________ (the thing you forgot last time) |
Eight rows is a cut, not a limit: when the table is full, the leftovers go on the back of the page, and the items that made the cut are the ones with a note attached.
The items that carry the day fit in one pocket. They get their own lines because they are the ones that get forgotten in the rush out the door.
| 1. | ____________ (the pocket they live in, so both pages agree) |
| 2. | ____________ |
| 3. | ____________ |
| 1. | ____________ (the one that only works the night before) |
| 2. | ____________ |
| 3. | ____________ |
Check what the event itself asks for. What belongs in the bag changes with the format: some conferences run on a laptop and a badge, some are online and the packing is a desk and a cable, and some organizers publish their own attendee guidance. The answer lives on the organizer's page, not on a printable. This sheet records what you decide to bring; it does not decide it.
These two pages are a packing sheet: item lines, packed circles, and boxes. They hold no event recommendations, no registration or ticket information, and no travel advice, and nothing here promises attendance, a spot, or a win at any event.
The bag table keeps gear straight, but it cannot tell you which conference to fly to, and it does not try. The calendar these sheets sit alongside is built that way on purpose, and its README opens with it:
“Curated calendar of 45 web3 hackathons, conferences and popup cities from September 2026 through Q1 2027, plus 2 bonus entries for mid-2027.”
- Web3 Events & Hackathons Calendar README, first sentence
The same README's data quality section carries the caveat that matters for a packing page like this one:
“Hackathon deadlines shift; always confirm on the registration URL before committing.”
Two pages cover one bag and one morning. The full Web3 Events & Hackathons Calendar covers the season the same way a checklist covers a bag: every entry written down in one place, with the same fields each time. It ships as a CSV with all 45 entries (name, dates, location, ecosystem, prize pool where announced, registration URL, and notes) that imports into Notion, Sheets, or Excel, plus a markdown version grouped by month for quick reading. Every entry was checked against an official organizer page or a major event aggregator on September 5, 2026; entries where only an approximate deadline could be confirmed are marked with a ~, and no dates or prize pools were invented. The free angles of the same pack: the hackathon prep checklist, the first hackathon tips for beginners, and the online hackathon list guide.
one-time · CSV + markdown · instant download · personal and commercial use, no resale of the calendar itself