GETTING A WORKFLOW OUT OF n8n.
n8n exports workflows as JSON, which is the right format for a machine and the wrong one for every person you need to show it to. These are the practical ways round that — images, embeds, handovers, and what the file actually contains before you send it.
How to export an n8n workflow as an image
n8n exports workflows as JSON, not pictures. Here is how to turn that JSON into a clean PNG, SVG or PDF of the canvas — by hand, from the CLI, or automatically in CI.
The n8n workflow screenshot problem
Screenshots of an n8n canvas crop, blur or capture the wrong thing. Here is exactly why, and how rendering the workflow from its JSON fixes it.
Embed an n8n workflow diagram in a README
Put a live picture of your n8n workflow in a GitHub README, Notion page or docs site — hosted at a permanent URL that re-renders itself when the workflow changes.
How to document an n8n workflow for a client
A repeatable way to hand over an n8n build: one overview diagram, one image per branch, annotated connections, and a PDF the client can actually read.
How to share an n8n workflow safely
Exported n8n workflow JSON can carry pinned customer data and inline API keys. Here is what is in the file, how to check it, and when to send a picture instead.
Export an n8n workflow to PDF or SVG
Print-ready and scalable exports of an n8n workflow — what PDF and SVG actually preserve, and which one to pick for a deliverable, a docs site or a poster.
Images for n8n templates and tutorials
If you sell or publish n8n templates, the picture is the product page. How to render listing images, thumbnails and social cards straight from the workflow.