HN Debrief

Show HN: TikZ Editor – WYSIWYG editor for figures in LaTeX

  • Developer Tools
  • Open Source
  • AI
  • Programming
  • Education

The post introduces TikZ Editor, a web and desktop app for editing TikZ figures visually while keeping the underlying LaTeX source in sync. TikZ is a code-heavy graphics language used in academic papers, and the usual workflow is tedious hand-editing of coordinates followed by repeated recompiles. The notable technical claim here is not simply WYSIWYG for TikZ. It is bidirectional editing that tracks exact source locations, so dragging an object can change only the numeric coordinates and leave line breaks, indentation, and surrounding code intact.

If your team ships papers, docs, or technical content in LaTeX, this is worth testing now because it lowers the cost of maintaining existing figures, not just creating new ones. The broader signal is that coding agents are starting to make niche, painfully tedious developer tools economically viable.

Discussion mood

Strongly positive. People saw a long-standing pain point in academic and technical writing finally getting a credible tool, and many were especially excited that it preserves hand-written TikZ instead of replacing it with opaque generated output. The only sustained criticism was that the generated code leans too hard on absolute coordinates, which clashes with how experienced TikZ users prefer to structure diagrams.

Key insights

  1. 01

    Absolute coordinates clash with idiomatic TikZ

    Experienced TikZ users pointed out that direct-manipulation editing naturally pushes the tool toward absolute coordinates, while good hand-written TikZ often uses anchors, relative positioning, and reusable structure. That is not a cosmetic complaint. It marks the boundary where WYSIWYG editing stops being a clean mapping onto the source language, because a drag gesture does not tell you which abstraction in the code should change.

    Use this as a maintenance and layout tool first, not as a guaranteed generator of elegant TikZ. If your figures rely heavily on relative layout or reusable constructs, expect some edits to still be easier in source view.

      Attribution:
    • gignico #1 #2
    • DominikPeters #1 #2
    • cubefox #1
  2. 02

    Preserving existing source is the real differentiator

    The standout value is not that you can draw with the mouse. It is that you can open old TikZ, make a tiny visual change, and keep the original file recognizable. That puts the editor in a different category from graphics tools that treat text formats as import-export containers and rewrite them on save.

    If your documents live in Git and figures are reviewed like code, prioritize tools that preserve human-written structure over tools that only optimize first-time creation. That will matter more over the life of a paper or documentation set than flashy editing features.

      Attribution:
    • Littice #1
    • DominikPeters #1
  3. 03

    Manual visual diffing still beats automated evaluation

    The author’s testing setup compares the editor’s JavaScript renderer against real LaTeX output converted with dvisvgm, but the last mile is still human inspection. Multimodal models were described as too unreliable at spotting rendering differences, and pixel diffs were too noisy because text rendering is never perfectly identical. The useful pattern here is that AI accelerated implementation, but verification stayed grounded in a reference renderer and human judgment.

    When building AI-assisted tools that emulate an existing system, keep a trusted reference implementation in the loop. Plan for human-guided discrepancy checks instead of assuming model-based or pixel-perfect evaluation will be reliable.

      Attribution:
    • aziis98 #1
    • DominikPeters #1
  4. 04

    The economics worked through subscriptions, not API pricing

    The project reportedly consumed about 700 million tokens and would have cost around $15,000 at API rates, yet the out-of-pocket spend was about $500 through ChatGPT subscriptions. That is a stark reminder that the practical cost curve for solo builders can look very different from list-price token math, especially for exploratory work with lots of iteration.

    If you are evaluating coding agents for internal tooling, model both API and subscription-style usage. The viability of a niche project can flip completely depending on which pricing path your team can use.

      Attribution:
    • DominikPeters #1
  5. 05

    Plugin support could unlock adjacent diagram ecosystems

    Interest quickly expanded beyond plain TikZ to pgfplots, CircuitikZ, tikzcd, and even note-taking integrations like Obsidian. The author said pgfplots is technically feasible but complicated by license incompatibility, since pgfplots is GPL while the editor is MIT, suggesting add-ons as the likely path. That turns this from a single editor into a possible platform for specialized technical diagram workflows.

    Watch the extension model more than the core feature list. If add-ons land cleanly, this could become infrastructure for domain-specific diagram editing rather than just a nicer TikZ front end.

      Attribution:
    • DominikPeters #1
    • lopsotronic #1

Against the grain

  1. 01

    Typst users want this for Cetz instead

    A real slice of the audience is already moving away from LaTeX and sees Cetz for Typst as the more interesting target. The pushback is not that the editor is bad. It is that the long-term opportunity may sit with newer document stacks that compile faster and feel less painful than TeX, even if they are not yet mature enough for a polished equivalent.

    If you are building around technical authoring, do not assume LaTeX is the only durable home for diagram tooling. Keep an eye on Typst adoption and design conversion paths early if portability could matter.

      Attribution:
    • __mharrison__ #1
    • DominikPeters #1
    • wjholden #1
    • tombert #1
    • hw__ #1
  2. 02

    Many users still prefer external diagram tools

    Not everyone wants to live inside TikZ at all. Some people have already standardized on draw.io, Mermaid, Xfig, or LyX because getting a decent figure quickly beats preserving a code-native diagram format. Even enthusiastic users asked for behavior like shape-attached connectors that they already expect from mainstream diagramming tools.

    A source-preserving editor solves one workflow, not the whole market. To win broader adoption, it will need to match the interaction quality people already get from dedicated drawing tools, especially around connectors and layout helpers.

      Attribution:
    • tombert #1 #2
    • DominikPeters #1
    • sureglymop #1
    • bedstefar #1
    • srean #1

In plain english

anchors
Named attachment or alignment points on a shape or node that other elements can snap or align to.
Cetz
A graphics package for Typst that plays a role similar to TikZ in LaTeX.
CircuitikZ
A TikZ-based LaTeX package for drawing electrical and electronic circuit diagrams.
Codex
An OpenAI coding-focused product or model line discussed as a developer tool.
dvisvgm
A tool that converts DVI or PDF-like output from TeX workflows into SVG vector graphics.
GPL
General Public License, a copyleft open-source license that requires derivative works to keep the same license terms.
Inkscape
An open-source vector graphics editor commonly used for editing SVG files.
LaTeX
A document preparation system widely used in academia and technical publishing for producing structured, high-quality PDFs.
LyX
A document editor that provides a graphical interface on top of LaTeX.
Mermaid
A text-based diagram language often embedded in Markdown for flowcharts, sequence diagrams, and similar visuals.
MIT
A permissive open-source software license with minimal reuse restrictions.
Obsidian
A note-taking and knowledge management app built around local Markdown files and plugins.
parser
Software that reads source text and turns it into a structured representation that a program can work with.
pgfplots
A LaTeX package built on top of PGF and TikZ for creating plots and charts from data.
relative positioning
Placing an object based on another object’s location instead of fixed page coordinates.
SVG
Scalable Vector Graphics, a text-based format for vector images used on the web and in design tools.
SVG renderer
A component that converts structured graphics data into SVG output for display.
TikZ
A LaTeX package and graphics language for drawing diagrams with code inside documents.
tikzcd
A TikZ-based LaTeX package for drawing commutative diagrams, often used in mathematics.
Typst
A newer markup-based typesetting system positioned as a simpler, faster alternative to LaTeX.
WYSIWYG
What You See Is What You Get, meaning an editor where the visual result is edited directly instead of only through source code.

Reference links

Alternative and specialized diagram editors

  • q.uiver
    Mentioned as a specialized visual editor for a narrower class of diagrams
  • TikZiT
    Cited as an existing specialized TikZ editor
  • CircuiTikZ Designer
    Shared as a focused editor for circuit diagrams in TikZ
  • tikzcd editor
    Mentioned as a visual editor for commutative diagrams
  • LyX
    Referenced as a long-used graphical authoring environment around LaTeX

TikZ ecosystem packages and references

Related tooling and integrations

  • presenst
    Shared as a Typst-based WYSIWYG presentation tool with a similar agent-built flavor
  • WireViz
    Mentioned as a complementary text-based wiring diagram tool used alongside CircuitikZ
  • TikZ Editor GitHub issues
    Provided for bug reporting after a Linux rendering issue