Record the bug instead of describing it

A written bug report is a reconstruction. A recording is evidence — the actual steps, the actual state, the actual thing that happened.

Free to use. Recordings are capped at three minutes and export at 720p with a watermark.

A screen recording of the OwnClip site marked up with arrows, a box, a highlighter sweep and numbered step badges, each appearing and leaving at its own moment — Arrows, boxes, highlighter and numbered steps, each on its own stretch of the timeline

The round trip you are trying to avoid

Report filed. "Cannot reproduce." Clarifying comment. "Which browser?" Screenshot attached. Two days gone on a bug that took forty seconds to trigger.

A recording carries the steps, the timing and the state at once, and removes most of the questions before they are asked.

Trim it down

Cut it to the reproduction.

Nobody watches a four-minute bug report. Trim the take to the steps that matter and the person reading the issue gets the failure in forty seconds.

The OwnClip video editor: a recording on the timeline with its filmstrip, the microphone and system audio waveforms on separate tracks below, and the tool panel open on the right — The editor the recording opens into — clips, both audio tracks, and the tools down the side

Smart Redact

Real data, blurred first.

Reproductions usually run against real records. A local scan finds email addresses, phone numbers and card numbers and offers them for review before anything leaves your machine.

A table of customer records with visible email addresses and phone numbers, scanned and then blurred in the OwnClip editor — Personal data found and blurred — proposed for review, never applied on its own

A useful bug recording

1Start before you reproduce itThe steps before the failure are usually the part that matters.
2Say what you expectedThe gap between expected and actual is the whole report, and it is faster said than written.
3Mark the failureAn arrow on the wrong value beats a paragraph describing where to look.
4Redact, then sendScan for anything sensitive, then share a link into the issue.

The OwnClip video editor with a recording on the timeline, a filmstrip of clips and the text and style controls open — The editor that opens on the recording you just made

Sharing

A link, into the issue.

The file uploads to your own Google Drive and you paste the link wherever you file the report. Access stays yours to revoke.

The OwnClip share dialog: a share link ready on view.ownclip.io, a Copy button, and a Disable link control in red — Sharing is the moment a recording leaves your Mac — and the link can be switched off again from here

Questions people ask

Usually, and a shorter recording gets watched. If a reproduction needs longer, Pro removes the limit.

Smart Redact scans for emails, phone numbers, card numbers and identifiers and proposes them for review rather than applying anything automatically. You can also blur any region by hand.

Sharing uploads to your own Google Drive and produces a link. Access is yours to control and revoke in Drive.

No. There are no issue-tracker integrations. You share a link and paste it wherever you file the report.

A screen recorder that keeps your work on your MacWhere recordings live, what runs locally, and what touches the network.Annotate your screen recordingsArrows, boxes, highlights and numbered steps, time-ranged.Show the answer instead of writing itShort recorded answers instead of long written ones.A screen recorder built for the MacThe hub: recording, editing and exporting on the Mac.