How I actually use a brain dump journal now instead of the three spreadsheets I had in 2019
I still remember the Sunday night I spent trying to rebuild my entire personal knowledge management system because Notion synced wrong after an update and half my backlinks were broken. That was the moment I stopped trying to make any tool do more than one thing. A brain dump journal is just that. One place where everything goes before you decide what to do with it. The free setup I describe below takes about twenty minutes once, and then it runs itself for years. The core idea is simple enough that people overcomplicate it. You keep a single document open permanently. When something enters your head, you write it down immediately without formatting, categorizing, or judging whether it belongs somewhere else. The sorting happens later, in a separate pass. The tool doesn't matter as much as the separation between capture and organization, which is why most people fail at this. They start filing things in their head while writing them down, which defeats the whole point. The point is speed. If you hesitate for more than five seconds between thinking and writing, you're not really brain dumping.
Free Brain Dump Journal Setup
Here is what I actually use right now. It costs zero dollars and runs offline on whatever device you already own. Option one: Apple Notes on iOS and macOS. Create a folder called "Dump." Inside it, create one note called "Inbox." Turn on "Open Last Note" in Settings so the app launches directly into that note every time. Use the quick note swipe from the lock screen on iPhone or the keyboard shortcut on Mac. This gives you sub-second access. I've been using this exact setup since 2021 and it handles everything from grocery lists to half-formed project ideas. Option two: Obsidian with the Canvas plugin, which is free. Create a new vault called "Brain." Inside, make a folder structure like this: Dump/ containing a note called "Daily," and Archive/ containing a subfolder for each month. The daily note is your active dump. At the end of each week, you move the content into relevant project notes or delete it. Obsidian's link syntax lets you wrap things in double brackets as you go if you want, but most of the time I just write plain text and deal with connections later. This works on Windows, Linux, Mac, and Android.
Option three: A plain text file in a git repository. This is what I switched to after the Notion collapse. A single file called dump.md in your home directory. Every entry is timestamped with a simple header. The git history is your audit trail. You can script a weekly parsing job that scans for keywords and moves lines into other files. This is the most robust option long-term because your data is never inside someone else's platform. The biggest mistake I see people make is building a dump system that requires tags, properties, or frontmatter at capture time. None of that belongs in the initial write. You are trying to empty your mind, not curate a database. The metadata conversation happens during the review pass, which should be a separate scheduled event, not something you try to do in the same sitting. I ran into a specific problem with the Apple Notes approach around mid-2023. I started having entries stack up to over 3,000 lines in the single Inbox note, and the app became noticeably slow when opening it. The workaround was straightforward. I split the archive into monthly notes and set a rule in my head: once the current dump note passed about 150 lines, I moved everything older than seven days into a dated note and started fresh. Performance went back to normal immediately. I wish I had done that from the start instead of ignoring the problem for three months.
Get the Full Details

Review frequency is where most free setups quietly break down. A brain dump that is never reviewed becomes digital hoarding. I recommend doing a review pass twice per week, twenty minutes each session. During the review, you read through recent entries and decide on one of three actions: delete it, move it into a project or context list, or convert it into a calendar action. If an item survives two review cycles without being acted on, it usually means you don't actually care about it, and deleting it is the right call. This is counter-intuitive for a lot of people who feel guilty about clearing things out, but the guilt is almost always misplaced. There are honest limitations to this approach that you should know before committing. A single-document brain dump doesn't scale well if you have more than about ten distinct life areas generating frequent entries. If you're juggling multiple jobs, side businesses, and a family schedule all at once, you will eventually need either multiple dump documents or a tagged system. I found this out the hard way when a freelance project and a personal renovation project kept colliding in the same note and I couldn't find anything for three weeks. The fix was splitting into two notes by context, which is a small structural change but a significant mental shift. Another limitation is that brain dumps don't handle time-sensitive items well. If your main overflow is meeting notes or scheduled reminders, a flat dump is the wrong tool. Use a proper calendar or task manager for those. The dump is for the unstructured stuff that doesn't fit anywhere else yet.
The real reason this works is that it removes the decision friction from capturing thoughts. Most people spend more energy organizing their todos than actually doing the work those todos represent. A free, simple, offline-first dump journal eliminates that overhead entirely. It won't fix a broken workflow, but it will stop the bleeding while you figure out what the actual workflow should be.