[Canvas] Export preview to PNG/PDF + useCanvasAction exportCanvas

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Feature request for product/service

Cursor IDE — Canvas (.canvas.tsx)

Describe the request

Canvas is great for agent-generated analytical artifacts (architecture reviews, metrics tables, flow diagrams). Today the source lives at ~/.cursor/projects/<workspace>/canvases/*.canvas.tsx, but there is no way to export the rendered preview (the panel beside chat) to shareable formats.

Requested capabilities (either or both):

A) UI export (highest priority)

  • Right-click (or ⋯ menu) on the Canvas preview panel:
    • Export as PNG
    • Export as PDF (multi-page if content scrolls)
  • Optional: Copy as PNG to clipboard
  • Save dialog defaults to the canvas file’s directory or Downloads
    Why: Screenshots are lossy and don’t match theme/layout; copying .canvas.tsx is useless for non-developer stakeholders.

B) SDK / programmatic export

Extend useCanvasAction() (from cursor/canvas) with something like:

dispatch({
  type: "exportCanvas",
  format: "png" | "pdf",
  path?: string, // optional; if omitted, show save dialog
});
5

Very common request we’re exploring! Out of curiousity, what would this bring you that Shared Canvases (a link) don’t?

7

Probably not everyone who needs to share is in Cursor’s team.

9

Strong +1 on this. To Colin’s question — Shared Canvases are great for the in-Cursor team workflow, but a PDF/PNG export covers a fundamentally different set of recipients and use cases that links can’t:

Stakeholders who aren’t Cursor users. I work in a large enterprise where canvases get used as research deliverables, architecture reviews, and decision artefacts. The people who need to read them — engineering managers, security, procurement, executives, external auditors — don’t have Cursor licences and won’t be getting them. A shared link is a dead end for that audience; a PDF lands in an email or a Confluence attachment.

Cross-team and external sharing. The current Shared Canvases scope is intra-team only. For anything that needs to leave the team boundary (cross-org review, vendor conversations, compliance evidence, board materials), a portable file is the only viable artefact.

Records of record. PDFs are versioned, dated, archivable artefacts that fit existing governance systems (Confluence, SharePoint, document management, regulatory submissions). Shared links are mutable and tied to Cursor’s availability; that’s the wrong shape for an evidentiary or compliance record.

Offline / air-gapped consumption. Plenty of enterprise environments don’t allow employees to authenticate into third-party SaaS dashboards from every device. A file does.

Programmatic export from agent runs. This is the bigger unlock. The useCanvasAction({type: "exportCanvas"}) half of the OP’s proposal would let agents generate a canvas as part of a pipeline and ship the rendered artefact alongside the run — research summaries, post-incident reports, weekly metrics decks. Today the agent has to be told “now also re-render this canvas as HTML and shell out to headless Chrome” every single time, which is fragile and lossy compared to letting Cursor render its own runtime.

Concrete recent example from our side: an agent produced a canvas comparing LiteLLM and 11 alternative LLM gateways for an internal architecture decision. The audience is enterprise IT architects and a security review board — none of whom are in our Cursor workspace. Shared Canvases couldn’t deliver to them; we ended up exporting via the window.print() devtools trick, which works but is not a workflow we can ask non-technical authors to repeat.

Both halves of the OP (UI menu + useCanvasAction export) would close the loop. UI export is the immediate value; the SDK action is what lets agent-authored canvases participate in automated pipelines.

Yes, this post was vibe texted with cursor :wink:

Sven

10

+1.

I’d love the ability to share a Canvas outside of my team. I often need to present architecture, flows, and designs to non-technical stakeholders who don’t have Cursor accounts.

A view-only share link (similar to Figma or Miro) would make it much easier to collaborate without requiring everyone to create an account.

Bonus points if it supported password protection, expiration dates, and optional commenting.

11

In the current version, the window.print() workaround does not work anymore. It crashes cursor completely and the app closes :confused: … So my only way atm is to ask cursor to export teh canvas as html so I can print it to PDF