An architecture diagram is a strange thing to send. It's usually the single most useful page in a proposal, an audit response or a handover pack — and it's usually also the page that describes, in labelled boxes, exactly how the system is put together. A PNG in an email is unreadable the moment the diagram is bigger than a laptop screen, a link into your wiki needs an account the recipient doesn't have, and a public paste site puts your service names and trust boundaries somewhere anyone can read them. Most diagramming tools will export to a self-contained HTML page, which gives you a fourth option: upload it, send one unguessable link, and let the reader pan and zoom their way around it on whatever device they happen to have open.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Export the diagram as a self-contained page. A Mermaid or D2 diagram rendered into a single HTML file with the styles and script inlined, a draw.io or Excalidraw export, a Structurizr or C4 view, or an SVG wrapped in a minimal page — anything that opens correctly when you double-click it locally will open correctly here. If it's a multi-file export, zip the folder and drop that instead; the entry page is detected automatically.
You get back a 32-character unguessable link carrying a noindex tag and an X-Robots-Tag header. That combination matters more for this kind of document than for most: a diagram carries service names, vendor choices, network boundaries and sometimes hostnames, all in text a crawler reads happily. Add a password when it's going into a security review, and an expiry when it's tied to an audit window or a procurement cycle — both free on every plan.
Then replace the file when the architecture moves, at the same address, with the password and expiry carried over. Diagrams age faster than any other document in a handover pack, and the failure mode is specific: somebody makes a decision from a diagram they bookmarked in March. Turn Review on and reviewers can pin questions directly on the box they're asking about, which beats a paragraph beginning "in the top-right area of the diagram".
The test is simpler than the tool list: export it, double-click the file, and see whether it opens correctly in your browser with no server running. Mermaid and D2 both render to a single HTML page with everything inlined. draw.io exports an HTML file, and Excalidraw exports an SVG you can drop into a minimal page. Structurizr and other C4 tooling produce static output. If a tool gives you a folder rather than one file, zip the folder and upload that — the entry page is found automatically and relative paths keep resolving.
For a small diagram, do — it's fewer steps and it renders in the email client. It stops working at exactly the point diagrams get useful: once there are more than a dozen labelled nodes, a flat image is either too small to read on a phone or too large to fit on a screen, and the reader is pinching and dragging a picture rather than reading a diagram. An HTML export keeps the text as text, so it stays sharp at any zoom, stays selectable and searchable, and stays legible on the phone where a surprising number of first looks happen.
It depends entirely on the link, which is the reason to be deliberate about it. What you want is an address nobody can guess, a no-index instruction where crawlers will actually read it, and no public directory to browse. That's the default here: a 32-character random URL, a noindex meta tag plus an X-Robots-Tag header, and no gallery or listing anywhere on the service. Add a password when the diagram is part of a security review, and set an expiry so it doesn't outlive the engagement. Treat those as the baseline for this document type rather than an optional extra.
Not absolutely, and nobody honestly can — a page that renders on someone's screen can be screenshotted. What you can do is make forwarding meaningfully harder and reversible: a password means the URL alone isn't enough, an expiry means a forwarded link stops working on a date you chose, and replacing or removing the file closes it immediately for everyone. If the diagram genuinely cannot leave a controlled environment, that's a data-room conversation rather than a link conversation.
That's much of the point. A self-contained diagram page opens in the mobile browser and pans and zooms with the text staying sharp, because it's rendered rather than rasterised. It's worth testing yours on a phone before sending — some exports set a fixed width that gets awkward on a narrow screen, and if the tool that produced it can be told to render responsively, that's a one-line fix now rather than an apology later.
Turn Review on for the document and reviewers can pin a note to the exact box or arrow they're asking about, with no account needed on their side. It suits diagrams unusually well, because almost every question about an architecture is a question about one specific component, and anchoring the question to that component removes an entire round of "which service do you mean". Replies thread, you mark things resolved as you answer them, and on Studio you can export the whole thread as markdown.
Zip the whole thing and upload it as a bundle — an architecture overview with several linked pages, a diagram plus its ADRs, a handover pack with a contents page. The entry HTML is detected automatically and internal links between the pages keep working, so the reader gets a small private site rather than a folder of files. That's usually a better handover artefact than a PDF, because the diagrams stay interactive and the links stay clickable.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.