u/DrummerAdditional330

I keep thinking about the gap between notes and files.

In most PKM systems, notes are treated as knowledge.

They can be linked, tagged, resurfaced, connected to projects, connected to people, connected to ideas. A note does not have to mean only one thing.

But files don’t behave like knowledge.

They behave like storage.

A file can be the result of thinking, but it often gets treated like something to be stored.

A PDF, a screenshot, a spreadsheet, a design export, a draft, a recording, or a small piece of code can contain just as much personal knowledge as a note. Sometimes it is the actual artifact that came out of the thinking.

But once it becomes a file, the system around it becomes much more rigid.

It needs a location.
It needs a folder.
It needs a name good enough to be found later.

That feels very different from how knowledge actually works.

The same file might matter because of a project today, a topic next month, and a completely different decision six months later.

In a note-taking system, that kind of overlap feels normal.

In a file system, it feels awkward.

I’ve seen people solve this in different ways: links from notes, PARA, tags, aliases, DEVONthink, Hookmark, project dashboards, or just very disciplined folder structures.

But I’m still wondering whether files are treated too much like static objects, when they are often part of a living knowledge system.

Maybe the question is not “where should this file go?”

Maybe it is:

“How should this file stay connected to the contexts where it becomes useful again?”

Curious how people here think about this.

Do files belong inside your PKM system, or do they stay as a separate layer that your notes point to?

I tried a small experiment with my file system for a few weeks because I was getting tired of constantly feeling like I should “organize better.”

I didn’t do anything fancy. I only changed 3 things:

- I stopped using deep folder structures
- I started giving files more descriptive names
- I did one short cleanup a week instead of trying to stay perfectly organized all the time

That was basically it.

What changed:

1. Saving got faster

I used to waste a weird amount of energy deciding the “right” folder for every file. Once I switched to broader folders, saving became much more automatic.

2. Finding things later got easier

This was the biggest one. It turns out I usually don’t remember where I saved something. I remember what it was about. So better filenames helped way more than better folder structure.

3. I felt less resistance around files in general

This surprised me the most. My old system always felt like it was quietly falling apart. This one feels a lot less “perfect,” but a lot more usable.

I think the mistake I was making before was assuming a good file system should make storage feel clean.

Now I think a good file system should make retrieval feel easy.

For me, that ended up meaning:

- broad folders
- better names
- search/recents doing most of the work
- small maintenance instead of constant maintenance

Not saying this is the best system for everyone, but it’s the first one that’s actually felt lighter instead of smarter.

Curious if anyone else ended up with something similar.