Skip to content

Publishing on the web

Vizzy diagrams don’t have to stay on your Mac. The Publish menu puts a document — or a whole workspace — on usevizzy.com, so you can send a teammate a link instead of a screenshot. You can also publish from the terminal; see Publishing from the CLI.

Publishing a workspace is private by default. It uploads the content and gives you a link, but until you share it, that link only works for you. Deciding who can read it is a separate step — see Who can read it below.

Publishing is tied to your account, so the first time you publish you’ll sign in with GitHub. The app and the CLI share one account — sign in on either and the other is signed in too.

The Publish menu has two paths:

  • Publish this workspace — publishes every document across the workspace’s watched folders and attached files as one browsable site, with a collapsible file-tree sidebar and a document switcher. New workspaces start private; Sharing… opens the controls. Copy link to workspace re-copies that link.
  • Copy link to this document — publishes the document you’re looking at as a public page and copies its link to the clipboard. This one is a public link by design; use “Publish this workspace” if you want to choose who can read it first.

Republishing updates the same link — publish again after an edit and the URL doesn’t change. Republishing never changes sharing you’ve already set up: a public workspace stays public, a code-protected one keeps its code, and the code itself doesn’t change. Cross-file links between published documents resolve and open in a new tab, and your vizzy.config theme travels with the workspace so published pages look like they do in the app.

Click Sharing in the top right of a published page you own, or on the workspace’s row in your libraryPublish ▸ Sharing… in the app opens the same dialog. There are three settings:

SettingWho can open the link
PrivateOnly you, signed in. The default for a new workspace.
Password-protectedAnyone who has the link and types the code.
PublicAnyone with the link.

Published pages are never listed anywhere and always carry noindex, so a public workspace is still not something a search engine will surface — “public” here means anyone with the link, not findable.

Choosing Password-protected generates a readable code like plum-otter-7k4mx. Send the link and the code — usually in different places — and the reader types it once. The unlock lasts 30 days in that browser.

There are two things to do with a code: copy it, or type a different one and save. Saving a new code, or switching away from Password-protected, immediately locks out everyone who unlocked with the old one.

A published page can be read two ways, chosen from the view-mode dropdown in the reader header:

  • Document (the default) — the file renders as a scrollable reading document: a readable column of full Markdown (headings, lists, quotes, tables, code) with the diagrams embedded inline and a floating heading outline.
  • Canvas — the same infinite, pannable canvas you see in the app.

The choice mirrors into a shareable URL — ?mode=document or ?mode=canvas — so you can send a link that opens straight into the view you want.

Every published diagram has an expand button: it opens that diagram alone in a full-screen pan-and-zoom modal, centered and fitted, for a close look at a dense diagram without the rest of the page around it.

Your library lists everything you’ve published, with each workspace’s current sharing setting on its row. Deleting a workspace there fully removes its published content from the web.