← Back to blog

Blog & updates

DrawFig FAQ — 20+ answers from first launch to TikZ export

2026-03-11

What DrawFig is, how it relates to draw.io, pricing, TikZ export, data import, online vs downloaded editor, and troubleshooting.

DrawFig FAQ — answers from first launch to TikZ export

Published: 2026-03-11 Category: Help / FAQ Reading time: ~15 min Tags: FAQ, DrawFig, TikZ, getting started

Introduction

New users usually ask: What is DrawFig? How is it different from draw.io? How does TikZ export work? Does it cost money? This English FAQ mirrors the Chinese mega-post: basic concepts → everyday features → technical tips → resources. For the exhaustive Chinese wording, see the Chinese FAQ (same slug, switch language with ?lang=zh).

Part 1 — Basics

Q1 — What is DrawFig?

DrawFig is a research-oriented diagram editor built on top of the draw.io engine, with extra libraries and export paths for scientists. Highlights - Graph / network / flow / state-machine oriented stencils - TikZ export for LaTeX papers - Optional structured import (JSON/CSV) for generated graphs - Free public tier aligned with drawfig.com positioning - Chinese-first UX (English UI strings follow ?lang=en) Typical users: CS/math grad students, LaTeX authors, data folks who need clean vector figures.

Q2 — DrawFig vs stock draw.io?

DrawFig forks / extends draw.io: same canvas DNA, added research affordances.
Area draw.io DrawFig
Core drawing Yes Yes
Research stencil packs Limited Expanded
TikZ export No Yes
Structured graph import Limited Stronger story
Graph auto-layout helpers Basic Tuned presets
CN localisation OK Deep
If you only need occasional boxes-and-arrows, stock draw.io is fine. If you publish graphs + LaTeX, use DrawFig.

Q3 — DrawFig vs FigDraw?

Topic DrawFig FigDraw
Price Free core Paid tiers
TikZ Yes No
Strength Graph theory, LaTeX Biomedical templates
Data import JSON/CSV pipelines Limited
Deep dive: comparison article.

Q4 — Do I need to “deploy” DrawFig?

No. There is no Docker image or server “deployment” step for everyday users.
  1. Online: open https://drawfig.com in a modern browser — usually no separate installer (needs network).
  2. Offline: download the editor + static webapp from the open-source repo, then open editor.html locally — that is “download + browser”, not ops-style deployment.
Developers may clone the repo and run the portal stack for their own intranet; that is optional self-hosting and not the default path described to end users. Ignore random docker run … drawfig/... snippets as a required workflow.

Q5 — Pricing / hidden fees?

The product is marketed as free for individual research use, including TikZ export and public icon packs. Optional revenue (donations, enterprise services, training) must not remove the baseline free tier — confirm on the live site for legal wording.

Part 2 — Everyday features

Q6 — TikZ export walkthrough

  1. Finish the figure on canvas.
  2. File → Export as → TikZ (exact menu path may vary slightly by build).
  3. Choose snippet vs full preamble, optional minification.
  4. Paste into your .tex, add \usepackage{tikz} + libraries hinted in the export header.
  5. Compile with TeX Live / Overleaf.
Tips - Start with tikzpicture-only snippets inside your existing class file. - Keep the .drawio source so you can regenerate after peer review.

Q7 — Importing graph data

Export nodes/edges from Python (networkx, custom scripts) as JSON arrays, import through the product’s data panel (wording varies by version), then run layout.

Q8 — Cloud save vs local files?

The public site may offer accounts and cloud saves; unauthenticated use often relies on browser storage — behaviour can change with product updates. Always download .drawio / exports before deadlines.

Q9 — Collaboration?

draw.io family supports real-time multi-cursor when wired to a backend; DrawFig inherits that capability when the operator enables it. Otherwise use Git + shared .drawio files.

Q10 — AI features?

Image-to-diagram / NL-to-graph features exist when the operator wires the optional AI service; without keys the UI entry may hide itself.

Q11 — Supported export formats?

PNG, JPEG, SVG, PDF, TikZ, and sometimes XML bundles for reuse in other tools.

Q12 — Custom fonts / LaTeX in labels?

Use built-in font pickers; some builds allow inline $...$ fragments — test per release.

Q13 — Large graphs (>200 vertices)?

Split into multiple canvases, or script layouts externally then import skeletons. Force-directed layouts get noisy beyond ~150 nodes unless heavily styled.

Q14 — Accessibility / colour-blind palettes?

Prefer colour-blind safe palettes; avoid red–green-only distinctions.

Q15 — Mobile support?

Editor targets desktop browsers; mobile is best-effort.

Data handling & privacy (no blanket guarantees)

  • This FAQ cannot promise that diagrams never leave your device, that no telemetry exists, or that data is never shared with third parties — all of that depends on which DrawFig instance you use, whether you authenticate, and the operator’s published privacy policy / terms of service and applicable law.
  • HTTPS helps against casual wire-tapping but is not a complete security story.
  • Back up important .drawio / PDF / TikZ exports; browser storage can be wiped when clearing site data.
  • Sensitive or regulated research data must follow your organisation’s compliance process; do not infer legal guarantees from informal blog/FAQ wording.
  • Open source improves inspectability of the codebase; it does not by itself warrant the behaviour of every third-party deployment.

Part 3 — Technical troubleshooting

Q16 — TikZ compile errors?

  • Load every \usetikzlibrary{...} mentioned in the export banner.
  • Remove duplicate \begin{tikzpicture} if you nest snippets manually.
  • Upgrade TeX Live if packages are stale.

Q17 — Blurry PNG exports?

Raise DPI to ≥300 for print, or export SVG/PDF instead.

Q18 — Connectors not snapping?

Enable magnet / connection constraints in the diagram inspector; reset edge waypoints.

Q19 — Blank editor or blocked assets when opening files locally?

If you open the downloaded editor.html via file://, some browsers block modules or XHR — use a tiny local HTTP server (e.g. python -m http.server) from the webapp folder, or use the hosted site. For operator-run mirrors, align origins with the deployment README and check the browser network tab for blocked requests.

Q20 — How do I get help?

  1. Email (preferred): write to support@drawfig.com with what you tried, expected vs actual behaviour, browser + OS version, and minimal reproduction steps. Attach screenshots or a small sample only if they contain no confidential data.
  2. Issue trackers (optional): for defects or feature ideas you may open an issue on the linked GitHub / Gitee repository — availability and triage cadence follow that repo’s README.
  3. Self-service: scan this FAQ and the on-site blog tutorials for known answers.
This FAQ does not promise fixed response SLAs (e.g. “48h on issues”). Channels not listed here may or may not exist over time; rely on the contact methods above.

Further reading

Changelog

  • 2026-03-11 — Initial Chinese FAQ published.
  • 2026-04-17 — English companion added (condensed; full detail remains in Chinese article).
DrawFig Team — questions? support@drawfig.com