Folding and zooming let a single long note behave like a stack of focused small ones. How the two operations work, and why they beat splitting files.
· Note-Taking Methods · 7 min read
Every long note eventually presents the same choice. It has grown past a screen or two, finding anything in it means scrolling and squinting, and working on one section means seeing four others out of the corner of your eye. At this point most people conclude the note is "too big" and split it into smaller files — which fixes the scrolling and immediately creates a different problem: the material that used to sit together now lives in five places, and every connection between the pieces has to be maintained by hand.
The choice is false. What you actually want is not smaller notes; it's the ability to see less at a time while the material stays together. Outliners have had this ability for forty years, in the form of two operations — folding and zooming — and they remain the most underused features in note-taking, mostly because people who come from documents never think to reach for them. This article is about what each one does, how they differ, and the working style that falls out once both are cheap.
Folding collapses a line's children underneath it, leaving just the line itself visible. Fold every top-level line of a three-hundred-line note and you're looking at eight lines — the note's table of contents, except you didn't write a table of contents, and it can never drift out of date, because it is the structure rather than a description of it.
The point of folding isn't tidiness. It's that a folded note answers a different question than an unfolded one. Expanded, a note answers "what exactly did I write?" Folded, it answers "what is this note about, and where does the thing I need live?" Those are different reading modes, and a document format forces you to do the second one by scrolling through the first — skimming past material at full detail to find the section you want. Folding lets you descend gradually: see the eight top-level lines, open the one that looks right, see its five children, open one of those. You read the note the way you'd walk a directory tree, except the leaves are your actual sentences.
There's a second use that matters just as much: folding while writing. When you're drafting one section, the other sections at full detail are noise — worse, they're an invitation to go fiddle with something you already finished. Folding everything except the branch you're working on turns a sprawling note into a page that contains only the current problem. Nothing was moved, deleted, or reorganized; you just told the note which parts to shut up.
And folding is what makes restructuring possible at all. You can't judge whether a note's shape is right while looking at it through a keyhole of one screenful of prose. Folded to its skeleton, a note's structural mistakes are visible at a glance — the two sections that are really one, the "misc" branch quietly eating everything — and, in an outliner, fixable in seconds. That interplay between seeing the shape and changing it is covered in Notes That Are Cheap to Rearrange; folding is the seeing half.
Zooming is the stronger dose. Where folding hides a branch's children, zooming hides everything except one branch: pick a line, zoom in, and that line's subtree becomes the entire visible document — its children promoted to top level, everything above and beside it gone. A breadcrumb trail remembers where you are, and zooming back out returns you to the full note with nothing changed.
The difference from folding is psychological as much as visual. A folded note still shows you the folds — you can see there are seven other collapsed sections, and part of your attention stays aware of them. A zoomed branch shows you nothing else exists. It has the phenomenology of a small, focused note: it starts at the top of the screen, it ends when the material ends, and every keystroke you make lands somewhere inside the one thing you're working on. If you've ever made a temporary file just to draft one section in peace and then pasted the result back, zooming is that maneuver as a single reversible keystroke.
This is what dissolves the big-note-versus-small-notes dilemma. The genuine argument for small notes was never storage; it was focus — a small note is a workspace that contains one thing. Zoom gives every branch of a big note that property on demand, without paying the cost small files impose: no navigating between them, no duplicated context at the top of each one, no wondering which of five fragments holds the paragraph you remember writing. One project note with clean top-level branches, zoomed into as needed, behaves like a folder of small notes that happen to share a single searchable, rearrangeable home. The tradeoffs around note size are laid out in How Big Should a Note Be? — zoom is the feature that moves the answer toward "bigger than you think."
Zooming also quietly fixes hierarchy fatigue. Deep nesting is unpleasant mostly because of what it does to the display: by level five, your text lives in a narrow column on the right side of the screen and the indentation guides outnumber the words. Zoomed into that fifth-level branch, it is level one — full width, no ancestry in view. The depth still exists in the structure, but you never have to look at it, which means you can let structure be as deep as the material honestly requires instead of artificially flattening it to keep the note readable.
The two operations correspond to the two postures you alternate between in any real work session, and it's worth being deliberate about the pairing.
Zoom in to produce. When the task is to write, draft, or think through one branch — the meeting agenda, the argument of section three, today's plan inside a long project note — zoom into it and stay there. The visible document now defines the task's boundaries, and finishing has a shape: you've handled everything on screen.
Zoom out and fold to evaluate. When the task is to decide what to do next, check coverage, or judge structure, zoom back to the full note and fold it to one or two levels. Now you're reading the map instead of the terrain: what's here, what's missing, what's grown enough to deserve restructuring, which branch to zoom into next.
The failure mode this rhythm prevents is doing both at once — the default state in a document, where you're simultaneously trying to write one paragraph and aware of the whole file. That split attention is why long documents feel heavy to work in even when the writing itself is going fine. Outliners don't remove the note's size; they let you choose, moment to moment, whether size is visible.
Mechanically, all of this only works if the operations cost nothing. In Indenta, folding is Ctrl/Cmd+↑ and ↓ on the current branch, and zooming is a click on any bullet — or Ctrl/Cmd+. and Ctrl/Cmd+, to move one level in and out, with Esc dropping you back to the full note and a breadcrumb showing the path down. The exact bindings vary by app and the User Guide has the full list; the requirement that doesn't vary is that both actions must be a reflex, not a command you look up, because their whole value is that you do them dozens of times an hour without noticing.
Take the longest note you have — the one you've been meaning to split. Fold it to its top level and read the skeleton. Some of those lines will surprise you; a structure nobody has looked at in months always drifts, and this is the first time you're seeing yours whole.
Then zoom into one branch and work there for a session — just that branch, as if it were the only note you own. When you zoom back out, notice what didn't happen: you never scrolled past finished sections, never got baited into editing something unrelated, never lost your place. Then ask whether the note was ever really too big, or whether you were just being shown too much of it at once.
Try it in practice: Indenta is a free, offline-first outliner — nested notes, backlinks, tags, and peer-to-peer sync, with no account required. Start writing in your browser, or read the User Guide first.