File attachments: keep documents with the work they support
Attach files from Google Drive and Dropbox directly to cards and tasks so your team always has the right documents at their fingertips.
Why attach files to cards?
Design mockups, specs, research documents, contracts, and other supporting files often live in cloud storage. When they are attached to the cards they support, the team does not need to search through shared drives or ask "where is the file for this?" in chat.
- Reduce context switching — find documents without leaving the board
- Keep supporting materials connected to the work they relate to
- Give every team member easy access to relevant files
- Preview files directly from the card detail view
Google Drive integration
Attach documents, spreadsheets, presentations, and other Google Drive files to any card or task. Files are linked by reference — the original stays in your Google Drive with existing sharing permissions intact.
- Open the card detail modal and use the attachment option to browse Google Drive
- Select one or more files to attach
- Attached files appear in the card detail with a preview and link to the original
- Team members click the attachment to open the file in Google Drive
- Removing an attachment does not delete the file from Google Drive
Example: A product card titled "Redesign checkout flow" has three Google Drive attachments: a Figma export of the current flow, a user research summary spreadsheet, and a product requirements document. Every developer working on the card has one-click access to all supporting material.
Dropbox integration
Teams using Dropbox can attach files the same way. Link design assets, shared documents, and media files to cards so they stay connected to the planning workflow.
- Browse Dropbox files from the card attachment interface
- Attach individual files or folders
- Attached files link to the Dropbox original with preview support
- Sharing permissions are managed in Dropbox — Flying Donut links by reference
Learn more about the Dropbox integration: Dropbox integration page · Google Drive integration page
Best practices
- Attach files during backlog refinement so the team has context when work enters a sprint
- Use descriptive file names — 'checkout-flow-v2-mockup.pdf' is more helpful than 'design.pdf'
- Remove outdated attachments when documents are superseded to avoid confusion
- Combine file attachments with card descriptions: reference the attached file in the description so people know what to read
- Use Google Drive for collaborative documents and Dropbox for static assets and archives
Common questions
Are files uploaded to Flying Donut?+
Can I attach files from both Google Drive and Dropbox on the same card?+
What file types are supported?+
Do attachments count against my Flying Donut storage?+
Keep your documents connected to your workflow
Attach files from Google Drive and Dropbox to cards and tasks so your team always has the right context.