All posts
Allen
Author, Content Operations Manager·Originally published Dec 4, 2025 · Updated Oct 9, 2026
A four-zone whiteboard delivered as a presentation, email attachment and review link

How to Export and Share Your Online Whiteboard in 8 Steps

Export a whiteboard as a static image when people need to see a finished decision. Share a live link when they need current context. Give named collaborators editing access—or an appropriate native export—when they need to change the underlying work. These are different deliveries: a readable attachment does not preserve editable shapes, and a view-only link does not prevent someone from keeping a copy.

This guide follows one fictional project, Harbor website launch, from a four-zone board to a presentation, an email attachment and a review link. You can rebuild it from the supplied text and diagrams.

Published by AFFiNE. Feature details were checked against the AFFiNE v0.27.4 stable release and its source on October 9, 2026. This is a source-reviewed workflow, not a hands-on test of every client. The illustrations are original diagrams, not product screenshots; cloud deployments and installed versions can differ.

Step 1: Plan Your Export Scope and Audience

Write one sentence before exporting: “This audience needs this part of the board to make this decision.” For Harbor, use these three briefs:

DeliveryAudience and questionScopeTradeoff
PresentationLaunch team: what happens next?Decisions and next actions, with a short overview firstLarger labels; less background detail
Email attachmentSponsor: is the plan approved?A clean summary image plus the decision in email textEasy to open; becomes a separate, dated copy
Review linkNamed reviewers: what needs correcting?A sanitized review document with contextCan stay current; access must be checked

A whole document includes more than the part currently visible on screen. A selection is the objects you chose. A frame is a composition boundary; it is not automatically a separate permission boundary or a PDF page. Keep private material in a separate document, not just outside the visible frame.

Use a filename such as harbor-launch-decisions-v1.png. Record the owner, review deadline and authoritative board location next to the file. Keep the exact format extension added by your export or image application.

Step 2: Prepare the Board for a Clean Export

Build the four-zone Harbor board

Create four named frames in a two-by-two layout in AFFiNE Edgeless. Use three short notes per frame. These are fictional planning details, not a customer case study.

ZoneNotes to copy
BriefGoal: explain the new homepage. Audience: existing customers. Constraint: use approved screenshots.
OptionsA: feature tour. B: problem → solution story. Choose B; retain A as an appendix.
DecisionsLead with the customer problem. Use one annotated screenshot. Keep pricing out of this board.
Next actionsMaya: draft the story, Tuesday. Leo: check the screenshot, Wednesday. Noor: approve the package, Thursday.

Connect Options → Decisions → Next actions. Use a pale background, dark text and one accent color. Keep the same zone names in every delivery so reviewers can refer to them unambiguously.

Harbor project board arranged into Brief, Options, Decisions and Next actions, with a clear path from options to action.

Rebuildable example diagram. The complete wording is in the table above and in the board blueprint and handoff checklist. This is not an AFFiNE import file.

Run a preflight check

  • Scope: include the title, decision, owner and deadline. Remove stray arrows and unused notes from the delivery copy.
  • Sensitive content: inspect embedded images, attachments, links and text, not just what is in the crop. Remove private material before making a review document public.
  • Fonts: wait for fonts and images to load. Open the result on the recipient's device if possible; substitute a simpler font if glyphs are missing.
  • Background: check light and dark destinations. Transparent pixels can make dark labels disappear on a dark slide. Use a solid background when that is safer.
  • Size: inspect the smallest label at its actual displayed size. A sharp image can still contain text too small to read.
  • Accessibility: put the decision and action list in selectable text beside the image. Do not make the image the only record.

Keep the editable master intact. Remove or simplify content in a delivery copy rather than flattening the only source.

Step 3: Choose the Right Export Format and Quality

What AFFiNE's checked stable release exposes

The v0.27.4 export menu distinguishes Doc from Edgeless. Do not use a generic list of file formats as a promise that every mode supports them.

Mode or routeSource-confirmed behaviorImportant boundary
Doc export menuHTML, Markdown, Copy as Markdown, PNG and SnapshotDocument output; not a selected whiteboard frame
Doc printPrint route is exposedPDF depends on the available print destination; inspect pagination
Doc direct PDFA separate PDF export is behind a feature flagDo not assume it appears in every installation
Edgeless document export menuHTML, Markdown, Copy as Markdown and SnapshotText/document exports do not promise canvas-layout fidelity
Desktop Edgeless selectionCopy as Image for selected content, including a frameUses desktop capture; browser-only use is not supported by this implementation
SVG, JPG or PPTX exportNot exposed by the menu reviewed hereDo not promise native AFFiNE export to these formats

A Snapshot is an AFFiNE/BlockSuite document archive (.bs.zip), with an export and import implementation. It is the appropriate route to evaluate for native editable reuse. Test an import into a separate document before relying on it; missing assets can still matter. It is not a universal editable file or a promise to preserve collaboration history and permissions.

Choose a static image for viewing, a live link for current context, or a native snapshot for editable reuse; each requires a different verification.

Choose by the recipient's task, then verify the output. A PDF containing a screenshot remains a raster image inside a PDF.

Set a pixel budget, not a vague “high quality” target

Suppose an image must occupy 1,200 pixels of a slide. A 600-pixel-wide capture must be enlarged, which can look soft. Start with at least the displayed width; if your actual export route supports a larger output, compare it at the final size. A 2,400-pixel image displayed at 1,200 pixels is a useful example, not an AFFiNE “2×” setting or a guarantee of readable text.

For a dense board, a tighter crop or two slides usually helps more than making one enormous image. AFFiNE's desktop Copy as Image implementation captures an area of the application window; it does not establish unlimited resolution or a user-selectable export scale.

The same four-zone board shown as an overview, then a closer Decisions and Next actions crop for presentation.

Keep the overview for orientation. Use the decision-and-action crop when people must read the details. The text above supplies the full accessible equivalent.

Step 4: Follow Platform-Specific Export Procedures

For an AFFiNE Doc

  1. Open the document you intend to deliver and let its assets load.
  2. Open its export controls, available through the document menu or the Share panel's Export area.
  3. Choose PNG for a document image, HTML or Markdown for text-oriented reuse, or Snapshot for native reuse. If the selected route exposes Print or PDF, inspect its output separately.
  4. Save the result, open the downloaded file, and check the title, bottom of the document, images and links. HTML/Markdown exports can include an assets ZIP; keep the package together.

For a desktop AFFiNE Edgeless selection or frame

  1. Open the sanitized board in the desktop application. Select the frame or objects needed for this delivery.
  2. Use Copy as Image in the selected content's menu. A frame selection is handled as its own capture area.
  3. Paste into your slide or image application. If you need an attachment, save a PNG from that application and open it again.
  4. Check the crop and actual pixel dimensions. For a whole-board image, select the intended board content and verify that every zone is present; a large selection may fit to the window and make labels small.

If the browser tells you the image-copy feature is unavailable, use the desktop client or a clearly identified operating-system screenshot of a sanitized view. A screenshot is a fallback capture, not proof of native PNG export from Edgeless. Neither procedure establishes one-click, multi-frame PDF export.

Viewing, editing and downloading are separate questions. A reader role concerns changes to the source document. It does not by itself prove that export, clipboard copying, screenshots or saving visible content are blocked.

The checked public-link control supports enabling read-only public access and disabling it. Treat that public link as forwardable. It is unsuitable for confidential material that must be limited to named recipients.

For invited collaborators, the member permission implementation distinguishes reader, editor, manager and no access. Available controls can depend on the workspace plan and deployment. Verify the roles offered in your workspace rather than assuming a separate commenter role, password, expiration date or domain restriction.

Permission workflow: inspect content, choose public or named access, check editing separately from copying, test as the recipient, then revoke and retest when finished.

Permission checklist, not a screenshot of available settings.

For the Harbor review, invite only the people who need the working document and grant the least access needed. If reviewers only need to read, keep feedback in an agreed channel alongside the link. If public access is intentional, publish only the sanitized review document.

Test a public link in a signed-out private window. Test named access as the intended recipient; a signed-out failure alone cannot tell you whether their account has access. Also check download/export options as that recipient. No independent “disable download” control was established in this review, so do not promise one.

Step 6: Share and Embed Exports in Drives, Chats, and LMS

Prepare these three packages from the same board:

Presentation: show the four-zone overview, then a larger Decisions + Next actions view. Use the example overview PNG and decision-and-action PNG as layout references or rebuild them with your own content. These are rendered companion diagrams, not exports produced by AFFiNE. Test the slide on the actual display; keep local copies for the meeting.

Email attachment: attach the decision-and-action image and write: “Harbor launch v1: use the problem → solution story and one annotated screenshot. Maya drafts Tuesday; Leo checks Wednesday; Noor approves Thursday. Please reply with corrections to these decisions.” Add the authoritative document link only if the recipient has access. Check any email or drive size limit before sending; there is no universal attachment limit.

Review link: send the sanitized document link with a specific question: “Please check Decisions and Next actions by Thursday. Is an owner or dependency missing?” State where feedback should go. Recheck access after copying the link from the final review document.

In a wiki, chat or LMS, put the dated preview beside the authoritative link and a text summary. An uploaded image is a snapshot; it does not automatically update when the whiteboard changes. If you host the attachment in a shared drive, its access is controlled by that drive as well as any access to the original board.

Step 7: Fix Common Export and Sharing Issues Fast

SymptomCheck firstRepair
Text looks softImage pixel width versus displayed widthCapture a smaller area; avoid enlarging a small image; split the board
Text is sharp but tinySmallest label in the actual slide/email previewEnlarge labels or show fewer zones
Cut-off arrows or notesSelection/frame boundary and paddingInclude the complete objects and capture again
Missing font or imageAsset loading and the reopened outputWait, retry, or use a simpler font; verify the saved file
Dark labels disappearTransparent image on a dark backgroundUse a solid light background in the delivery
Image copy unavailableBrowser versus desktop, installed versionUse the supported desktop route or label a screenshot fallback
Reviewer cannot open linkExact account, document and current roleCorrect the intended person's access; do not make confidential content public
Attachment is too largeDimensions and embedded picturesReduce unused canvas or split sections, then recheck legibility
Shapes cannot be editedWhether the recipient received an imageProvide named editor access or test a native Snapshot import

A PDF extension does not prove vector content, selectable text or editable whiteboard objects. Open it, zoom in and try selecting text before claiming those properties.

Step 8: Unify Creation, Export, and Sharing with AFFiNE

Keep the source board, a text decision record and delivery log together. For Harbor, record: version v1, owner Noor, the three deliveries, the intended audiences and the Thursday review deadline. This preserves the useful connection between the document and visual workspace without treating every output as interchangeable.

When review ends, remove unnecessary collaborator access and disable public access if it is no longer needed. Retest the old public link signed out. A person may still have access through membership or another role, so check that separately.

Revoking a link does not recall an exported file. Downloaded images, forwarded attachments, screenshots and imported copies can remain with their recipients. Correct the source, issue a clearly named replacement and ask recipients to stop using the earlier version when necessary. Avoid sending sensitive data in the first place.

Frequently Asked Questions

How do I export an entire AFFiNE whiteboard?

Distinguish the whole document from a visual capture. Snapshot exports the document for native reuse. In desktop Edgeless, select the content for a Copy as Image capture, then inspect it; large selections can become hard to read. HTML or Markdown output is not a guarantee that the spatial board layout survives.

Can I export an AFFiNE whiteboard as SVG or a multi-page PDF?

Those Edgeless delivery paths were not established by the stable menu and selection code reviewed here. Use a verified image capture, or place separate captures into a slide/document tool if you need a PDF handout. That is a conversion workflow, not native multi-frame PDF export.

Does view-only access prevent downloads or copying?

Do not assume so. Check any explicit export controls separately and test as the recipient. Even when a download button is absent, visible information can be captured. Use access restrictions and sanitized content together.

What should I send if the recipient needs editable objects?

Use named editing access to the original document, or test AFFiNE's native Snapshot export/import in a separate document. A PNG or a screenshot inside a PDF is not an editable whiteboard. Check assets after import and arrange permissions separately.

Related Blog Posts