Creating a capture

When you open the Capture widget, a toolbar appears at the bottom of your screen with two options: take a screenshot or start a screen recording.

Taking a screenshot

Click the screenshot button to capture the current state of your screen. Capture will take a snapshot and move you directly to the preview screen where you can add details.

Recording your screen

Click the recording button to start capturing a screen recording. You'll have the option to include additional context:

• Microphone audio - Narrate what you're doing or explain the issue as you record
• Webcam video - Show your reactions or provide a face-to-camera explanation alongside your screen

Once you're ready, click start and perform the actions that demonstrate the bug. Click the stop button in the toolbar when you're finished.

Adding details and configuring destinations

After capturing a screenshot or recording, you'll see a preview of what you've captured. Here you can:

Annotate your screenshot - If you captured a screenshot, use the toolbar on the left to highlight specific areas or add text comments pointing to exactly where the issue occurred. This helps developers understand exactly what you're reporting.

Add a description - Explain what went wrong, what you expected to happen, or any other context that will help your team understand the issue. This is optional but recommended.

Choose where it goes - By default, bug reports use the destination settings configured for your capture key. You can customize:

• Which space in Capture.dev to save the report to
• Integration-specific options like project, tags, or issue status for connected tools (Linear, Jira, etc.)

If you haven't specified a custom capture key, these settings default to your team's configuration from the integrations settings page.

When you're ready, click Send to publish your bug report.

After sending

Once published, your bug report appears immediately in Capture.dev and begins syncing to any enabled integrations.

[Screenshot: Capture complete screen with copy link button and integration status]

You'll see:

• A link to the bug report in Capture.dev that you can copy and share with your team
• Links to tickets in connected tools (like Linear or Jira) as they're created

It's safe to close the window while integration links are still being generated - they'll be available in your Capture dashboard after they are generated.

Bug reports from guests

If you're using Capture to collect bug reports from customers or users who aren't on your team, parts of the flow are hidden to protect your team's internal data.

The capture process works the same way - guests can take screenshots, record their screen, use annotation tools, and add a description. The key differences happen behind the scenes:

For privacy, guests don't see:

• Destination settings
• Integration options for Linear, Jira, or other connected tools
• Links to third-party integrations after sending

What happens automatically:

• Bug reports use the default settings for your capture key
• Reports are published to Capture.dev immediately
• Integrations sync in the background if "auto-publish" is enabled for an integration.
• Guests receive a link to copy and share.

INFO

Guest users cannot view the bug reports they create unless your team has enabled public link access in team settings. This keeps your bug reports private by default while still allowing guests to submit them.

Next steps

Want to customize what additional context gets captured alongside screenshots and recordings? See Custom Context to add custom metadata like user IDs, environment details, or application state.

Already have bug reports flowing in? Learn how to connect integrations to automatically route them into Linear, Jira, Slack, and other tools your team uses.