Sharing Diagrams Without a Server

How a share link works

ArchBoard has no server to store a shared diagram, so the diagram travels inside the link. It is compressed, then encrypted with AES-GCM using a random key, and both the ciphertext and the key are placed in the part of the URL after the hash sign. Browsers do not send that part to servers, so the site hosting ArchBoard never sees your diagram.

View and edit links

A view link opens a read-only canvas with a button to save a copy into the recipient's own workspace. An edit link opens a fresh copy straight away. Either way the recipient's changes never flow back to you, because there is nothing to sync with.

What a link does not protect

Anyone who holds the entire link can read the diagram, because the key is inside it. Treat the link like a password: send it through a channel you trust, and do not put it in a public ticket. There is no revocation, since there is no server to revoke it on.

Size limits and alternatives

Links work for small and medium diagrams. The dialog warns once the link passes about eight thousand characters, because some chat apps truncate long URLs, and refuses above thirty two thousand. Turning off images shortens a link dramatically. For anything larger, export a file, such as an editable PNG or SVG with the scene embedded, or a backup.

Choosing between link and file

Use a link for quick feedback on a modest diagram with someone you trust. Use an exported file when the diagram is large, when you need an archive or when the recipient should be able to keep it without relying on a URL surviving a chat tool. Whichever you choose, remember that exporting is always your decision; nothing in ArchBoard leaves the browser by itself.

Try it with a template

• Zero Trust Access
• OAuth 2.0 Login Flow