Knowledge Concepts
What is the PARA method? A clear explanation of Tiago Forte's organizational framework — Projects, Areas, Resources, Archive — and how to implement it in any note-taking tool.
The PARA method is an organizational framework for digital information, developed by Tiago Forte, that sorts everything into four top-level categories: Projects (active work with a deadline), Areas (ongoing responsibilities without a deadline), Resources (topics of interest for future reference), and Archive (inactive items from the other three) — organizing information by actionability rather than by topic or type.
PARA stands for Projects, Areas, Resources, Archive. It works across any note-taking tool, any cloud storage system, and any project management platform.
Tiago Forte developed the PARA method as part of his "Building a Second Brain" system, first published as a blog post in 2017 and later in his book of the same name (2022). Forte was frustrated by the inconsistency of topic-based organization: should a file about "marketing" go in a "Marketing" folder or a "Client XYZ" folder? The answer was often arbitrary, making retrieval unreliable.
His insight: organize by actionability, not topic. Where something belongs should be determined by how you'll use it, not what it's about. An article on Python programming might belong in:
The same content; different categories depending on your current situation. PARA is a living system, not a static filing cabinet.
Definition: A series of tasks linked to a goal with a deadline.
Examples: Launch the Q3 marketing campaign, write the annual performance review, plan the team offsite, finish the client proposal.
Key test: Does it have a deadline or a clear endpoint? If yes, it's a Project.
Projects are your active work. When you open your second brain to do work, you mostly navigate via Projects.
Definition: A sphere of activity with a standard to be maintained over time — no endpoint.
Examples: Health, finances, team management, writing (as an ongoing practice), relationship with key clients, professional development.
Key test: Is this something I'll always need to manage? If yes, it's an Area.
Areas don't end — they're ongoing responsibilities. Your "Health" area never closes. Your "Team Management" area continues as long as you have a team.
Definition: A topic or theme of ongoing interest that doesn't fit into your current Projects or Areas.
Examples: UX design (you're interested but not currently working on a UX project), history of the printing press, recipe collection, PKM tools.
Key test: Is this useful to a future version of me, but not immediately actionable?
Resources are your "someday/maybe" knowledge: things you want to be able to retrieve if the need arises, but that you're not actively using.
Definition: Inactive items from the other three categories.
Examples: Completed projects, responsibilities you no longer have, topics you're no longer interested in.
Key test: Is this no longer active? If yes, archive it (don't delete — retrieval value persists).
Archive is not a trash bin. It's a cold storage for potentially valuable reference material. Completed projects often contain decisions, research, and context that future projects will reference.
| Category | Active use? | Time horizon | Example |
|---|---|---|---|
| Projects | Daily | Weeks to months | "Launch new pricing page" |
| Areas | Regular | Ongoing indefinitely | "Financial management" |
| Resources | Occasional | Whenever relevant | "SaaS pricing patterns" |
| Archive | Rarely | Historical reference | "2024 pricing page project" |
The key workflow: When you capture something (an article, a note, a document), ask: does this relate to an active Project? If yes, put it there. If not, does it belong to an Area? If not, is it a Resource? If not, Archive.
When working on a task, navigate to the relevant Project. Need reference material? Check the relevant Area or Resource folder.
A freelance UX consultant using PARA:
Projects folder:
Areas folder:
Resources folder:
Archive folder:
When working on the Fintech project: she opens "Fintech app redesign for Client A" and everything relevant to that project is there — research, wireframes, client emails, notes, references. She's not searching across the whole system.
When writing the case study: she opens that project folder. When she needs reference patterns, she opens "UX patterns and research" in Resources.
"PARA replaces topic-based organization." Partially. PARA is the top-level structure. Within a Project or Resource folder, you can organize by topic if that's useful. PARA provides the outer shell; internal organization within categories is flexible.
"I need to migrate all my existing notes to PARA first." Start fresh. Create the four PARA folders. For new captures, route them into PARA immediately. Existing notes can stay where they are until you naturally encounter them while working. Forced migration of thousands of existing files is a procrastination trap, not a productivity strategy.
"Resources is where everything goes if I don't know what to do with it." Resources should require a purpose-oriented question: "Could I imagine using this for a future Project or Area?" If yes, Resources. If no, it shouldn't be saved at all. Resources that never get accessed aren't resources; they're noise.
"PARA is perfect for everything." PARA is excellent for knowledge workers with multiple active projects and ongoing responsibilities. It's less obviously suited to highly creative practices (artistic projects don't always have deadlines) or to single-domain specialists who don't maintain many different Areas. Like all systems, it's a starting point, not a universal truth.
Step 1: Create four top-level folders (or sections, notebooks, spaces, depending on your tool) named Projects, Areas, Resources, Archive.
Step 2: List your current projects — everything with a defined goal and deadline. Each gets a sub-folder under Projects.
Step 3: List your current areas — ongoing responsibilities. Health, finances, team management, client relationships, professional development. Each gets a sub-folder under Areas.
Step 4: List your key resource topics — subjects you want to be able to reference. These are the seedbed of future knowledge.
Step 5: Archive completed projects and inactive areas. Move old project folders to Archive. Move areas you no longer maintain to Archive.
Step 6: Route new captures immediately. When saving something new, ask: does this serve an active Project? If yes → Projects. If no → Areas, Resources, or Archive.
PARA works in any tool that supports nested folders or categories:
Forte recommends applying PARA consistently across all your tools, not just your notes app — so your file system, email (where possible), and task manager all share the same organizational logic.
For users who save web content, WebSnips's collections can map to PARA categories:
The Connections graph surfaces relationships across your collections — useful for finding connections between Resources that could serve an active Project.
Creator Studio generates content from selected saves within a collection — making WebSnips most useful for the Projects layer, where saved research directly feeds deliverables.
Can I use PARA with Obsidian? Yes — PARA works well in Obsidian as a folder structure. Projects, Areas, Resources, Archive become root-level folders with sub-folders for individual items. Many Obsidian users combine PARA folders with the Zettelkasten linking method: PARA provides the outer structure, Zettelkasten provides internal linking within Resources.
How often should I move things between PARA categories? Whenever your situation changes. A Resource becomes a Project folder when you start actively working on that topic. A Project moves to Archive when it's complete. An Area moves to Archive when the responsibility ends. Review PARA structure weekly — Forte's "weekly review" includes confirming that Projects, Areas, and Resources are correctly populated.
What's the difference between Projects and Areas? The deadline/endpoint test. A Project has a clear finish: "Launch the website" is done when the website launches. An Area doesn't: "Maintain the website" continues indefinitely. When people confuse Projects and Areas, it's usually because something that's actually ongoing (an Area) is framed as a project that never completes.
Should tasks also be in PARA? PARA is for notes and reference material, not for task management. Your task manager (Todoist, Things, Linear, Notion tasks) handles tasks. Tasks are linked to Projects by name, but PARA folders hold the reference material for those projects, not the tasks themselves.
The PARA method — Projects, Areas, Resources, Archive — is an organizational framework that sorts all information by actionability, making retrieval and use more intuitive than topic-based filing systems.
The key insight: where something belongs should depend on what you'll do with it, not what it's about. The same article on Python programming belongs in a Projects folder when you're writing a Python tutorial, and in a Resources folder when you're not.
Implement PARA in 20 minutes: create four folders, list your active projects and areas, start routing new captures appropriately. Retroactive migration isn't required.
More WebSnips articles that pair well with this topic.
What is citation management? A clear explanation for researchers and academics — how citation managers work, the best tools, and how to avoid the most common mistakes.
What is tacit knowledge? A clear explanation for team leads and ops people — what tacit knowledge is, why it's the hardest knowledge to transfer, and practical methods to make it explicit.
What is a commonplace book? A clear explanation of the centuries-old knowledge collection practice, famous examples, and how to build a modern digital version for writers and researchers.