What Pixtex is.
Pixtex turns n8n workflow JSON into pixel-perfect PNG, SVG, JPEG, WebP and PDF images — in the browser, or through a render API, CLI and GitHub Action.
What it does
Pixtex is a developer tool: an image exporter for n8n workflow diagrams. n8n itself exports workflows only as JSON, and has no built-in image export. Pixtex fills that gap by rendering the workflow the way it looks on the n8n canvas and returning an image file.
Step-by-step walk-throughs — exporting a workflow as an image, embedding a self-updating diagram in a README, documenting a build for a client — are in the guides. API keys are self-serve at pixtex.dev/developers, where the full API reference lives.
Five ways to run it
- Web editor
- Upload or paste workflow JSON, or connect an n8n instance and pick a workflow. Style the canvas, then export or share. Free, no account required.
- Render API
POST https://api.pixtex.dev/v1/renderwith an API key returns image bytes. Hosted images get permanent, updatable URLs for embedding in READMEs and docs, and a permanent page to send to a client.- CLI
npx pixtex render workflow.jsonandnpx pixtex push, from the npm packagepixtex.- GitHub Action
VicegerentPrince/pixtex@v1, to re-render workflow images in CI.- n8n community node
n8n-nodes-pixtex, a verified node (see below), to render workflow images from inside n8n itself.
The verified n8n node
Verified nodes are manually vetted by n8n for security and quality, so on n8n Cloud you can add Pixtex straight from the node panel — no self-hosting and no manual install. See it on npm.
Is Pixtex a verified n8n node?
Yes. n8n-nodes-pixtex is a verified n8n community node — it passed n8n's manual security and quality review and is available on n8n Cloud with no manual install.
How do I add Pixtex inside n8n?
Open the node panel in any workflow (press N, or the + button), search for "Pixtex", and add the node marked with the verified shield. It renders any workflow into a share-ready image — or a permanent, updatable hosted URL — from inside n8n via the Pixtex render API.
Every Pixtex package — the n8n node, the pixtex CLI, and the GitHub Action — is published with npm provenance: a cryptographically signed, publicly verifiable build attestation that ties each release to the exact source commit and GitHub Actions workflow that produced it.
Nothing is locked in
Pixtex is one person's project, which is a fair thing to be wary of. So the honest answer to “what happens to my work if this stops” is: nothing, and that is a property of how it is built rather than a promise about next year.
- JSON in, an image file out.
There is no Pixtex format and no project to migrate. The input is the file n8n already gives you; the output is a PNG, SVG, JPEG, WebP or PDF on your disk. how the export works →
- No account to make, so none to close.
The editor needs no sign-up at all. An API key is an opt-in for automation, and it is stored as a hash — the key itself exists only in your terminal. the API docs →
- Revoke a key and its hosted images go with it.
Hosted images are owned by the key that created them. Revoking cascades: the URLs stop resolving and the files are deleted, in one action, without asking anyone. keys and hosted images →
- Share links delete themselves after 24 hours.
A share is a temporary object by design — the workflow behind it is removed when the link expires, whether or not you remember to do anything. what is in a workflow export →
Who made it
Pixtex is built and operated by Muhammad Muneeb, who goes by VicegerentPrince online. It launched at pixtex.dev in July 2026.
See what it produces
Drop a workflow JSON file on the editor and export a PNG, SVG or PDF — or read the reference and render it from a script instead.