Inkscape is the only figure tool most labs use that costs nothing and still exports every file format Nature asks for: .svg, .pdf, .eps and .ps with editable layers, plus 300 dpi RGB raster when a journal wants pixels. It runs on Linux, opens the SVG your matplotlib or ggplot2 script already wrote, and nobody will ever email your PI about a seat license. It is also the tool most likely to eat a Saturday. Inkscape hands you a blank canvas and a very deep toolbox; it does not hand you a starting diagram, a receptor icon, or any opinion about what your figure should look like. This is an honest accounting of that trade in 2026 — what Inkscape does better than paid alternatives, where the hours actually go, and how to decide which side of the trade you are on before the deadline decides for you.
Why Inkscape keeps showing up in methods sections
Two reasons, and neither is nostalgia.
The first is format. When Nature says "we require vector files with editable layers" and lists .ai, .eps, .pdf, .ps, .svg as acceptable, Inkscape writes four of those five natively. Its working format is SVG — not a proprietary container that exports to SVG, but plain SVG on disk that you can diff in git, patch with a script, or open in a browser five years from now. For a file that has to survive three rounds of review and a production editor's house-style pass, that matters more than any feature list.
The second is provenance. Your figures usually start as code output. Matplotlib writes SVG and PDF. ggplot2 writes SVG and PDF. MATLAB writes both. Open any of those in Inkscape and every tick, every line, every axis label lands as a real, selectable vector object. You are not tracing a screenshot; you are editing the same geometry your analysis produced. That is the cleanest possible path from data to publication figure, and it is free.
Add the ecosystem. The Scientific Inkscape extension pack by David Burghoff (UT Austin ECE) has 925 stars on GitHub and shipped release v1.4.25 in June 2026 — a set of eight extensions built specifically for this workflow. The Scaler resizes a plot's data area without touching its text or tick sizes, which is the single most annoying thing about assembling multi-panel figures by hand. The Homogenizer forces one font, one font size, and one stroke width across a whole selection. The Autoexporter watches a folder and re-exports SVGs to your target formats every time you save, which is how you keep a LaTeX manuscript's figures current without thinking about it.
None of that costs anything. So why does anyone pay?
Where the hours actually go
"Slow" is not an insult here. It is a specific, reproducible set of frictions, and if you have used Inkscape for a real paper you have hit all four.
The blank canvas is the biggest cost
Inkscape ships with no scientific asset library. No cell membranes, no mice, no organs, no pipettes, no signalling-pathway motifs. If your figure is a schematic — a mechanism, an experimental setup, a model diagram — you are drawing every element with the Bézier tool from zero. This is where BioRender earns its subscription honestly: a curated, scientifically vetted icon library is a real product, and searching inkscape scientific figures because you want that library for free is a category error. Free software does not make a drawing appear.
For plot assembly and annotation, the blank canvas costs you nothing, because the plot already exists. For schematics, it can cost you a day per figure until you build a personal template library — and most people never do, because the next paper is always more urgent.
Imported PDF and EPS text arrives broken
This one surprises people. Import a PDF-format plot and the text arrives structurally wrong in ways that only become obvious the moment you try to change a word. The Flattener extension exists precisely to undo them:
| What you see after importing a PDF plot | What is actually in the file | Flattener option that fixes it |
|---|---|---|
| The whole x-axis behaves as one label you cannot edit | Every tick number sits in a single text object, each character positioned individually | Split distant text and lines |
| A title in three pieces that drift apart when you drag them | One line of text stored as several separate objects | Merge nearby text |
| Retyping a label makes its letter spacing collapse | Manual kerning baked into every string | Remove manual kerning |
| A superscript drops to full size when you edit it | Superscripts drawn as offset text rather than real markup | Merge superscripts and subscripts |
That is a fix, and a good one — but it is also a fix you have to know exists, install, and run before you can edit a single word.
Complex figures get sluggish
Inkscape's own community documents this plainly: plots with thousands of elements — scatter points, error bars, dense line traces — make the editor behave sluggishly. The Combine by Color extension was written to merge same-styled paths into one path specifically to restore responsiveness and shrink file size. Practical translation: a 5,000-point scatter plot is a figure you fight rather than edit. Rasterizing that one layer before assembly is usually the right answer, and it is one more decision you have to make.
CMYK still is not really there
Inkscape 1.4 improved CMYK-to-RGB conversion and added limited support for Adobe colour palettes containing CMYK values, but full CMYK output remains limited. For most submissions this is a non-issue — Nature explicitly asks for RGB at 300 dpi or higher — but if you are producing a print cover, a CMYK-mandated society journal figure, or a poster at a print shop with a hard CMYK requirement, you will be converting outside Inkscape.
One more scheduling note: Inkscape 1.4 is still the current stable branch as of September 2026, with 1.4.4 as the latest bugfix release. Version 1.5 — which brings a standardised multipage format and document tabs — is in the development branch, with an alpha targeted for the end of October 2026. Do not plan a submission around 1.5 features.
An honest comparison, as of September 2026
Prices verified against each vendor's own pricing page in September 2026. Prices may change; we re-check monthly.
| Inkscape 1.4 | Adobe Illustrator | FigPad | |
|---|---|---|---|
| Cost | Free, GPL | US$263.88/yr, annual plan prepaid | $19/$25/$39 per month; $9/$15/$31 per month billed annually |
| Where the artwork comes from | You draw it | You draw it | Prompt, sketch, or reference image |
| Native working format | Plain SVG on disk | .ai (proprietary) |
Cloud project, exports out |
| Vector export journals accept | SVG, PDF, EPS, PS | AI, PDF, EPS, SVG | Layered SVG (Plus and Pro tiers) |
| Editable PPTX for lab meetings | No | No | Yes — objects stay editable in the slide |
| Raster export | Any DPI you set | Any DPI you set | 2K (Starter) / 4K (Plus) / 8K (Pro) PNG |
| Scientific asset library | None | None | Generated, not a fixed library |
| CMYK | Limited | Full | Not offered |
| Learning curve | Steep | Steep | Shallow |
| Offline | Yes | Yes | No |
| Publication rights | Yours, no restrictions | Yours, no restrictions | Included on all paid tiers |
The row that decides most arguments is not cost. It is row two: where the artwork comes from. Inkscape and Illustrator are both excellent at manipulating vector art that already exists. Neither of them will produce the first draft of a schematic for you.
A decision framework that takes thirty seconds
Answer these in order and stop at the first yes.
- Is your figure assembled from plots your code already produced? Use Inkscape. Import the SVG, run the Flattener, run the Homogenizer for uniform fonts, use the Scaler to match panel widths, export. This is Inkscape's home turf and nothing paid does it better.
- Do you need CMYK output, or Illustrator-specific artwork from a collaborator? Use Illustrator, or convert at the end.
- Is the figure a schematic you have to invent from scratch, and is your deadline this week? Generating a first draft and editing it beats drawing from zero — assuming the output is genuinely editable afterwards, which is the whole question.
- Everything else? Inkscape. It is free, and the skill compounds across your career.
How FigPad fits
FigPad does not compete with Inkscape at vector editing. It competes at step zero — producing an editable first draft of a schematic so you are never staring at an empty canvas at 11pm.
The part that matters for people reading this article is what comes out. A FigPad figure exports as layered SVG on the Plus and Pro tiers — meaning text is still text, arrows are still arrows, each label its own object. Open that SVG in Inkscape and you get exactly the editing experience described above, without having drawn anything first. It also exports PPTX where the shapes land in the slide as editable objects, which is the format your PI will ask for the day before the lab meeting, and 2K/4K/8K PNG depending on tier. There is a vectorizer for turning a bitmap you already have into editable paths, and a mode that turns a PDF paper into a conference poster draft.
Cost behaves differently too. FigPad charges credits per action rather than per seat: one generation is 2 credits, a text correction is 2 credits, and editing elements on the canvas is free — re-exporting the same version costs nothing after the first export. Exporting an editable SVG is 4 credits. A typical generate → revise → export cycle lands around 16 credits, against a Plus monthly allowance of 300 credits (roughly 150 generations). Every paid tier includes publication rights, with no separate "publishing" upsell and no per-figure fee; FigPad's terms state you own the outputs generated for you, and that your prompts, sketches and uploads are not used to train its models. New accounts get free credits with no card required.
If you want the specifics before committing, the pricing page lists what each tier includes, the AI scientific figure generator page shows the generate-then-edit loop, and the tutorials walk through the SVG-and-PPTX export path end to end.
One caveat we will not soften: some journals now ask authors to disclose AI-assisted figure creation. Check your target journal's policy, and never present a generated illustration as primary experimental data. That rule applies whether the tool is FigPad, Illustrator's generative features, or anything else.
When you should stay with Inkscape
Plenty of cases, and we would rather you know them now.
Your figures are plots, not schematics. If ninety percent of your display items are matplotlib or ggplot2 output with annotations layered on, generation adds nothing. Inkscape plus the Scientific Inkscape extensions is the correct stack, full stop.
You need reproducibility and version control. Plain SVG on disk, tracked in git, diffable, scriptable via inkscape --export-* on the command line. No cloud tool matches that. If a reviewer asks how a figure was produced two years from now, the file itself is the answer.
You have no budget and no deadline pressure. Free is free. The learning curve is real but finite, and Inkscape skills transfer to every SVG task for the rest of your career.
You work offline, on a plane, or on a secured network. Inkscape does not need an internet connection or an account.
You need CMYK, exotic path operations, or precise typographic control. Inkscape's node editing, boolean operations and path effects go far deeper than any generation tool's canvas.
Your institution already licenses Illustrator. Then the money argument disappears and you should use whichever of the two you are faster in.
The strongest setup, honestly, is both: generate the schematic draft, export layered SVG, and finish it in Inkscape where you have full control. The two tools solve different halves of the same problem, and nothing stops you from using them in sequence — see also our scientific figure creator overview for where that handoff sits in a full submission workflow.
Key Takeaways
- Inkscape's format support is not the compromise. It writes SVG, PDF, EPS and PS with editable layers — four of the five vector formats Nature lists as acceptable — and any DPI raster you specify. Free does not mean journal-unfriendly.
- The cost is time, concentrated in schematics. Inkscape has no scientific asset library. Assembling existing plots is fast; inventing a mechanism diagram from an empty canvas is not.
- Install Scientific Inkscape before your next figure. The Flattener repairs clumped and manually kerned text from imported PDFs, the Scaler resizes plot areas without distorting text, the Homogenizer unifies fonts and stroke widths, and the Autoexporter keeps your manuscript's figures current.
- Know the two hard limits. CMYK support is still limited in 1.4, and figures with thousands of elements get sluggish — rasterize dense scatter layers before assembly.
- Pick by where the artwork originates. Code-generated plots → Inkscape. Invented schematics on a deadline → generate an editable first draft, then finish it in Inkscape. Anything that ends as a flat PNG has failed either way.
