Direct File URLs

Any URL that ends in a media-file extension can be pasted directly. The app fetches the file with a normal HTTP request, saves it to the board folder, and places it on the canvas.

Supported extensions

The match is on the URL path, not the response Content-Type. URLs that end in a non-media extension but redirect to media (some CDNs do this) are best pasted via their final media URL.

How it works

The fetch follows redirects, respects Content-Length for the progress indicator, and writes the response straight to disk. There is no transcode — the file is exactly the bytes the server returned.

Tips

• CDN URLs from blogs or news sites — most major image CDNs (Imgix, Cloudinary, AWS S3, Vercel image) allow direct fetch. Right-click the image in a browser → Copy image address to get the right URL.
• GitHub raw URLs — raw.githubusercontent.com/... URLs work fine for screenshots and assets.
• Notion / Figma / Slack file URLs — usually require auth; not directly pasteable. Download the file locally first and drag it onto the canvas.

Limits

• Auth-protected URLs (S3 signed URLs that expired, Google Drive without share-with-anyone) return 403 and the paste fails.
• HTML pages that look like media URLs (some galleries have .jpg in the path but serve HTML) fail with a content-type mismatch warning.

Where to go next

• Bulk-add files from a folder instead of one-by-one URLs — Connected Folder Sync.
• Upload local files — Uploading Local Files.