TikZ Editor Makes LaTeX Figures Less Painful

By Rogier Muller07.06.26
TikZ Editor Makes LaTeX Figures Less Painful

Dominik Peters’s TikZ Editor is a web and desktop editor for LaTeX figures. Its README describes editing existing TikZ, synchronized visual and source views, and preservation of formatting during visual changes. It also identifies partial support for decorations, graphs and plots, and says advanced let operations are not implemented. Check the constructs in your own figure rather than assuming every valid TikZ document is supported.

Updated 21 September 2026: consolidated the two TikZ guides, linked the maintainer's repository, and added explicit source-preservation and feature-limit checks. The exercise below has not been executed for this article.

Choose an existing figure with a known output

Pick a small diagram already included in a paper that builds successfully. Save the starting source and render the relevant page before editing. Use a figure with the features your project actually relies on, such as named styles, a reusable macro or a loop.

Make one visible change: move a label, adjust an arrow endpoint or change a node position. Avoid asking the editor or an agent to regenerate the entire diagram. A narrow change makes it possible to judge whether the tool preserved the rest of the source and output.

The project README describes source preservation as a feature. Treat it as a property to check on your input, not a guarantee that an arbitrary house macro will survive unchanged.

Review the text and the rendered page

Compare the saved source with the edited file. Confirm that names, comments, style definitions and repeated structures remain understandable. A figure can look correct while its source becomes harder for the next author to maintain. Conversely, a tiny diff can introduce an overlapping label or clipped arrow.

Run your paper's existing build command. For a project already using latexmk, a trial might look like this; replace the paths with real files:

latexmk -pdf paper.tex
git diff -- figures/model.tex

Inspect the actual PDF page, not only the editor preview. The surrounding document may supply fonts, packages or macros that change the result. Check captions, alignment, clipping and neighboring content at the final page size.

Give a coding agent the same constraints

If an agent helps with the diagram, name the intended visual change and require it to preserve existing structures unless a rewrite is part of the task. Ask it to report the changed source, document build result and any unsupported feature it encountered. A repository instruction can request this handoff; it does not itself verify the output.

Check Accept when
Meaning The diagram still expresses the intended relationship
Source Names, macros, loops and styles remain maintainable
Scope The diff matches the requested adjustment
Build The actual paper compiles with the edited figure
Rendering The final page has no new clipping or overlap

If the editor cannot preserve a construct, make that adjustment directly in source or simplify it deliberately with the author's agreement. Retain the visual workflow where it saves coordinate work without making the maintained artifact harder to understand.

Where does your team stand?

Each team member completes the proficiency matrix individually. You receive a PDF with the team baseline and a recommended next step.

Assess your team