PARA was created by Tiago Forte, the writer behind Building a Second Brain. He defines it as "a simple, comprehensive, yet extremely flexible system for organizing any type of digital information across any platform." The name is an acronym for its four buckets: Projects, Areas, Resources, and Archives.
The idea that makes PARA different is its organizing principle. Forte says to organize by actionability, not by subject. Rather than topic folders like "Psychology" or "Marketing," he advises you to "organize it according to the projects and goals you are committed to right now." That one shift is why the method scales across your whole digital life.
PARA is also deliberately tool-agnostic. Forte says to "use it in every one of the many places where you store information, such as your computer's file system, a cloud storage platform (e.g., Dropbox or Google Drive), or a digital notetaking app." In the wider Building a Second Brain framework, PARA is the "Organize" step of the C.O.D.E. system (Capture, Organize, Distill, Express), which is described as working "in any app or platform you prefer to use."
Here are Forte's exact one-line definitions of projects areas resources archives, the four categories that make up the system:
Evernote frames the same four buckets in more practical language: a Project is "a series of tasks linked to a specific outcome, typically with a deadline," Areas are ongoing responsibilities like health or finance, Resources are articles, tutorials, and reference materials, and Archives hold completed or inactive items.
| Bucket | Time horizon | Has a goal? | Example |
|---|---|---|---|
| Projects | Short-term, active | Yes, with a deadline | Launch new website by August |
| Areas | Ongoing, no end | No, a standard to maintain | Health, finances, your team |
| Resources | Whenever useful | No, reference only | Saved articles on design |
| Archives | Inactive | No longer | Last year's finished project |
This is the single most common source of confusion in PARA, and even critical reviewers flag it. The distinction is about accountability, not subject.
Take "cooking." If you are responsible for feeding your family every day, cooking is an Area, an ongoing standard you maintain. If you just collect interesting recipes for someday, cooking is a Resource. Same topic, different bucket, decided entirely by whether you carry ongoing responsibility for it.
A quick rule: Areas have a standard to uphold; Resources do not. Health is an Area because there is a level you are trying to keep. A folder of articles about nutrition is a Resource because nobody is failing if you never read them.
Todoist's implementation gives a clean five-step setup that works in practice. Here it is, adapted so it applies to notes and files as well as tasks:
Todoist uses simple examples worth stealing: dog training is a Project, your exercise routine is an Area, and book notes are a Resource. If you want the deeper capture-and-distill workflow that surrounds this, see our guide on how to build a second brain.
Ainotely is a free AI second brain that automatically titles, tags, and links your notes, so the sorting step of PARA mostly does itself. You capture; it organizes.
Try Ainotely freeThe origin sources are thin on complete examples, so here is one worked all the way through for a freelance marketer. Notice how related work lands together by action, not by topic:
| Bucket | What goes in it |
|---|---|
| Projects | Redesign Acme's landing page (due Aug 15), Write Q3 newsletter, Plan two-week Japan trip |
| Areas | Client relationships, Personal finances, Health and fitness, Professional skills |
| Resources | Swipe file of good ad copy, SEO articles, Notion templates, Japan travel guides |
| Archives | Last year's completed website project, A cancelled client proposal, Old fitness plan |
See how the Japan trip appears as an active Project, while general Japan travel guides live in Resources? When the trip is over, both move to Archives. That flow, from Resource to Project to Archive, is how PARA stays lean over time.
This is the question Forte's own post never directly answers, so let me address it head on. Folders, tags, and PARA are not competing tools. They operate at different levels.
| Approach | Organizes by | Main weakness |
|---|---|---|
| Topic folders | Subject (Marketing, Health) | Active work gets buried inside broad topics; you dig to find what matters now |
| Tags | Flexible labels, many per item | Powerful but easy to over-create; no clear home for each item |
| PARA | Actionability (is this live?) | Needs a judgment call on each item; the Area vs Resource line can blur |
The practical answer: use PARA as your top layer, then use folders or tags inside it. Your four PARA buckets are folders. Inside Projects, each project is a subfolder. Tags then cut across everything for cross-topic retrieval, for example a "client-acme" tag that links a live Project to reference material in Resources.
If you lean heavily on links and tags rather than folders, you may also want to read how PARA compares to a Zettelkasten method setup, since the two solve different problems and can coexist.
Because PARA is meant to be used in any app, it maps cleanly onto both popular tools.
You have two clean options. The simplest is four top-level pages, one per bucket, with sub-pages inside. The more powerful option is a single database with a "Category" select property set to Project, Area, Resource, or Archive, plus filtered views so each bucket has its own board. The database approach lets one note move between buckets by changing a property rather than dragging pages around. For a deeper walkthrough, see our Notion second brain guide.
Obsidian favors folders and links, so the natural setup is four top-level folders named 1 Projects, 2 Areas, 3 Resources, and 4 Archives (the numbers keep them in order). Your daily notes and links live inside those folders, and you archive by dragging a folder into Archives when a project closes.
Whatever the tool, the golden rule is the same: move things to Archives instead of deleting them. Archiving keeps your active workspace clean while preserving anything you might need later, which is exactly the future-reference purpose Forte gives the Archives bucket.
A candid critical review of PARA surfaces real pain points but stops at complaints. Here are those same problems turned into fixes.
Fix: ask "am I responsible for maintaining a standard here?" Yes means Area, no means Resource. Do not overthink it; you can move the item later.
The review warns to "be careful not to go into too much detail, or you risk complicating a system that is intended to be simple." Fix: keep to the four buckets plus one level of subfolders inside Projects. If you are three folders deep, you have gone too far.
Fix: default to the most actionable bucket. If something relates to a live project and a general topic, put it in the Project now; it can drop back to Resources or Archives later. Never let a single item stall your whole system.
The same review notes that PARA setup and maintenance "can be time-consuming." Fix: a five-minute weekly review. Move finished projects to Archives, promote any Resource that became a live project, and clear your inbox. This is the maintenance step tool-brand pages leave vague, and it is what keeps PARA working long-term.
Forte argues PARA endures precisely because "it gives you more time than it takes." That is only true if you keep the weekly review light and resist the urge to over-engineer.
PARA is a system created by Tiago Forte for organizing any type of digital information into four categories: Projects, Areas, Resources, and Archives. Its core idea is to sort information by how actionable it is right now, rather than by subject.
PARA was created by Tiago Forte, the productivity writer behind Building a Second Brain. He describes it as a simple, comprehensive, yet extremely flexible system for organizing any type of digital information across any platform.
An Area is an ongoing responsibility you are accountable for, such as health or finances. A Resource is a topic you are interested in but not responsible for, such as saved articles or reference material. The test: if you would feel bad neglecting it, it is an Area.
Folders and tags usually organize by subject, which scatters related work across many topics. PARA organizes by actionability instead, so everything tied to your current goals sits together. You can still use folders or tags inside PARA to hold each of the four buckets.
In Notion, create four top-level pages or a database with a category property for Projects, Areas, Resources, and Archives. Add each new page under one bucket, and move pages to Archives when a project or interest goes inactive instead of deleting them.
The most common mistakes are confusing Areas with Resources, over-categorizing into too many subfolders, freezing when an item seems to fit two buckets, and deleting old items instead of archiving them. Simple decision rules fix each one.
The purpose of PARA is to make information easy to find and act on by aligning your files with your current projects and goals. Tiago Forte argues it endures because it gives you more time than it takes to maintain.
Related reading: PARA method for your second brain, the best second brain app, and the Building a Second Brain book summary.
Sources and method: Tiago Forte, fortelabs.com PARA post; Building a Second Brain, PARA page; Evernote, What is the PARA method; Todoist, PARA method setup; Design Bootcamp, critical PARA review. Researched July 2026.