If the “classic tools” list from @waldgeist felt a bit heavy, here’s a different angle: minimize friction and context switching.
1. Use what you already live in
If you spend your day in:
-
Notion / Markdown / wikis
Try sticking with integrated diagram syntaxes like Mermaid where possible. It keeps your flows right beside the doc, versionable, and searchable. The tradeoff is less pixel-perfect control, but the payoff is zero paywall drama and dead-simple updates. -
Office ecosystem (Word/PowerPoint)
The built‑in shapes + connectors are actually decent. You can build a reusable “flowchart slide” or template and duplicate it. Not glamorous, but it ships fast and your coworkers already know how to edit it.
2. One “heavy” tool, one “light” tool
Instead of hunting “the best free flowchart tool,” think:
- Heavy: For big process maps, audits, swimlanes. Something with layers, snapping, alignment, and good export.
- Light: For quick 5‑minute flows during calls, then paste to a doc or slide.
For the heavy slot, a lot of people land on diagrams‑style tools because they strike a decent balance between complexity and cost. Pros for this type of tool:
- Free to use for a ton of scenarios
- Big shape libraries and templates
- Good exports to PNG, SVG, PDF
- Runs in browser so no install fights with IT
Cons:
- UI can feel crowded during long sessions
- Performance drops a bit with huge diagrams
- Not as “pretty” out of the box as Figma or similar
For the light slot, your best bet is often:
- Whatever your note app offers (inline diagrams, ASCII, screenshots)
- A simple canvas like PowerPoint/Keynote/Google Slides with boxes and arrows
3. Where I slightly disagree with @waldgeist and the other reply
They lean a bit more toward “pick one main tool and stick to it.” I’d argue:
- Have two tools: one frictionless, one powerful.
- Accept that “perfect” is the enemy of “documented.” Most flows do not need BPMN or UML; they need clarity and the ability to be updated in 30 seconds.
4. A simple decision filter you can use today
Ask yourself:
-
Do I need real‑time collaboration on almost every diagram?
- Yes → Stay browser based (Google‑style tools, diagrams‑style editor, or Figma).
- No → A desktop app or integrated syntax is safer from feature creep and paywalls.
-
Do I care more about beauty or speed?
- Beauty → Figma‑style tools on free tiers.
- Speed → Integrated text‑based diagrams or basic office shapes.
-
Am I okay with a few limits as long as I never hit a hard paywall surprise?
- If you hate even soft nudges to upgrade, favor open source or office‑built solutions.
- If occasional limits are fine, mix a browser editor with your main doc system.
If you set up one “serious” template and one “quick sketch” template in your chosen tools, you’ll spend a lot less time researching and a lot more time actually mapping your processes.