Hit Workflowy's 100-node monthly limit? Here's what to do

Workflowy’s free Basic plan includes all features, but it gives you 100 new nodes each month. When you reach that count, you can still add a node, but Workflowy shows a subscription prompt. That is not a disaster. It is a decision point.

If Workflowy is the right tool for the way you think, paying for it may be the cleanest answer. If the monthly count makes you second-guess ordinary capture, though, take that feeling seriously. An outliner should make it easier to get a thought down, not make each new line feel like a budget decision.

Here is how to decide without turning it into a migration project.

Upgrade when Workflowy is still the fit

Workflowy’s pricing page lists Pro at $8.99 per month, or $6.99 per month when billed annually. Pro removes the node and upload limits. That is a reasonable purchase when Workflowy’s particular way of working is already your system.

Stay and upgrade if these are true:

• You like how Workflowy feels day to day and are not looking for a different model.
• Your shared outlines, search habits, and shortcuts already live there.
• The subscription costs less than the friction of moving a tool that works.

There is no virtue in replacing a useful outliner just to avoid paying for it. The useful question is whether you are happy with Workflowy except for the cap, or whether the cap exposed a wider mismatch.

Do not make your outline smaller to fit the plan

The tempting response is to use fewer nodes. Put several actions on one line. Delete old project detail. Save quick thoughts somewhere else until next month. Those workarounds change the behavior that made an outliner useful in the first place.

An outline earns its place when it can hold the rough version of the work: a meeting note under the project it belongs to, a next action under that note, a question under the action. A monthly node count makes that natural shape feel expensive. If you find yourself compressing thoughts to save bullets, the limit is affecting the work, not just the bill.

That does not mean you need to move your whole account. It means you should try a live branch somewhere that will let you work normally.

Export one working branch before moving anything else

Workflowy makes this low-risk. Its export guide says you can export a single bullet or your whole account as Markdown or OPML. Start with one active project, your weekly planning root, or an inbox you regularly touch. Keep the archive where it is.

Save an OPML export as a .opml file, then open the listlis import panel and put it into a new top-level section. The app accepts Workflowy OPML, and it also accepts Markdown files. The goal is not to reproduce every corner of an older workspace. It is to find out whether a plain tree feels better when you are doing actual work.

Give the trial a real shape:

This week
  Website refresh
    Rewrite pricing page
      Notes from Tuesday's call
    Review signup flow
  Personal
    Book dentist appointment

Then add lines as they occur. Press o to add a sibling below the current row and Tab to nest it. Press Shift-Enter when a line needs a Markdown body instead of more children. Press ! to turn an action into a todo, then c when it is complete. Completion rolls up through the branch, so a finished project reads as finished without a separate task board.

The distinction is small but useful. You are not trying to make every thought fit a monthly tally. You are letting the structure follow the work.

A one-week trial gives a real answer

A useful trial has an active project, a normal capture habit, and an end date. It does not need an archive migration, a fresh folder system, or a feature-by-feature audit. The project should be messy enough to produce notes, tasks, and changes of plan. That is the work an outliner has to carry.

By the end of a week, two things become clear. You will know whether reaching for o and Tab feels natural when the project changes, and whether the plan remains easy to scan after the notes arrive. You will also know whether the monthly count was the real objection to Workflowy or only the first annoyance you noticed.

The result can go either way. A trial that sends you back to Workflowy makes the Pro decision easier, because it tells you the familiar tool is worth its price. A trial that keeps growing in listlis shows that the smaller working surface may fit better.

What listlis changes, and what it does not

listlis is for people who want the outline itself to stay central: one keyboard-first tree for tasks, notes, and half-formed ideas. A node has a title and an optional Markdown body. You can nest as deeply as the project needs, move a whole branch without dragging, share a subtree, or search when you need to find it again.

It is not the better choice if what you value most is Workflowy’s existing ecosystem or its exact interaction model. It is also not a replacement for a field-heavy database or a backlink-first knowledge graph. Those are different jobs. The Workflowy alternatives guide maps the broader choices, and the Tana alternative guide explains why a structured database may still be the right call.

For an ordinary project, though, the test is simple. Can the plan, its notes, and its next actions live in one visible shape? Can you add the next line without considering the count? If that is what you wanted from Workflowy in the first place, a small trial will answer more than another comparison table.

Keep Workflowy open while you test. Export the one branch you need, work from it for a week, and leave the rest of your account alone. If listlis feels lighter, keep going. If it does not, you still have your system and a clearer reason to upgrade Workflowy.

Open a root in listlis and try it with one live project. For the wider field, the outliner comparison hub keeps the honest cases for Workflowy, Logseq, Dynalist, Tana, and Roam in one place.