
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.
Write one sentence before exporting: “This audience needs this part of the board to make this decision.” For Harbor, use these three briefs:
| Delivery | Audience and question | Scope | Tradeoff |
|---|---|---|---|
| Presentation | Launch team: what happens next? | Decisions and next actions, with a short overview first | Larger labels; less background detail |
| Email attachment | Sponsor: is the plan approved? | A clean summary image plus the decision in email text | Easy to open; becomes a separate, dated copy |
| Review link | Named reviewers: what needs correcting? | A sanitized review document with context | Can 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.
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.
| Zone | Notes to copy |
|---|---|
| Brief | Goal: explain the new homepage. Audience: existing customers. Constraint: use approved screenshots. |
| Options | A: feature tour. B: problem → solution story. Choose B; retain A as an appendix. |
| Decisions | Lead with the customer problem. Use one annotated screenshot. Keep pricing out of this board. |
| Next actions | Maya: 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.
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.
Keep the editable master intact. Remove or simplify content in a delivery copy rather than flattening the only source.
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 route | Source-confirmed behavior | Important boundary |
|---|---|---|
| Doc export menu | HTML, Markdown, Copy as Markdown, PNG and Snapshot | Document output; not a selected whiteboard frame |
| Doc print | Print route is exposed | PDF depends on the available print destination; inspect pagination |
| Doc direct PDF | A separate PDF export is behind a feature flag | Do not assume it appears in every installation |
| Edgeless document export menu | HTML, Markdown, Copy as Markdown and Snapshot | Text/document exports do not promise canvas-layout fidelity |
| Desktop Edgeless selection | Copy as Image for selected content, including a frame | Uses desktop capture; browser-only use is not supported by this implementation |
| SVG, JPG or PPTX export | Not exposed by the menu reviewed here | Do 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 by the recipient's task, then verify the output. A PDF containing a screenshot remains a raster image inside a PDF.
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.
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.
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 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.
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.
| Symptom | Check first | Repair |
|---|---|---|
| Text looks soft | Image pixel width versus displayed width | Capture a smaller area; avoid enlarging a small image; split the board |
| Text is sharp but tiny | Smallest label in the actual slide/email preview | Enlarge labels or show fewer zones |
| Cut-off arrows or notes | Selection/frame boundary and padding | Include the complete objects and capture again |
| Missing font or image | Asset loading and the reopened output | Wait, retry, or use a simpler font; verify the saved file |
| Dark labels disappear | Transparent image on a dark background | Use a solid light background in the delivery |
| Image copy unavailable | Browser versus desktop, installed version | Use the supported desktop route or label a screenshot fallback |
| Reviewer cannot open link | Exact account, document and current role | Correct the intended person's access; do not make confidential content public |
| Attachment is too large | Dimensions and embedded pictures | Reduce unused canvas or split sections, then recheck legibility |
| Shapes cannot be edited | Whether the recipient received an image | Provide 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.
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.
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.
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.
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.
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.