A Minddrift product · macOS & iPhone

Find the ninety seconds that matter.

Your dashcam has been recording faithfully for years. It has also left you thousands of one-minute files with names like 20260901_135000.mp4 and no way into them. DriveReel turns that into drives you can search — and evidence that still counts as evidence.

1 Hz
telemetry, read from the video
0.30 g
hard-braking threshold
On-device
where the analysis happens
Never
how often we re-encode
What people actually need from footage

Nobody opens a dashcam folder for fun.

They open it because something happened, and a specific question needs answering — usually under pressure, often with somebody waiting.

  • At the kerb Was I moving when he hit me?
  • Next morning Who scratched the door in the car park?
  • Adjuster's email What time and where, exactly?
  • Disputed fault What colour was the light?
  • Hit and run Can you read the plate?
  • Two weeks later Is that clip still on the card?
01

Three afternoons that ruin a week.

Each one is a different question, and each one needs a different thing out of the same pile of files.
Scenario one · The rear-end

He says you reversed into him.

You stopped at a light. He went into the back of you. By the time the police arrive he is telling a story where you rolled backwards, and it is your word against his.

The footage exists. It is spread across two files, because the impact happened eleven seconds after a clip boundary, and the minute that proves you were stationary is in the previous file.

You needThe forty seconds before the impact, across the clip boundary, unedited.
AndYour speed at each of those seconds — from the camera's own GPS, not your memory.
DriveReelChains the clips back into one drive, so the boundary stops existing. The speed trace sits under the picture and reads 0 mph for the eleven seconds that matter.
Scenario two · The car park

Something scraped the door while you were inside.

Nine hours of parking mode. The camera woke on motion four hundred times — every trolley, every passing shopper, every headlight sweep. One of those four hundred is the one.

You have no idea what time it happened. You were in a meeting. Scrubbing nine hours at 8× is most of an evening, and you will probably miss it anyway.

You needNot nine hours. The handful of moments where something came close to your car.
AndTo know which of those the camera's own sensor thought was an impact.
DriveReelCollapses the night into one row, marks the fragments where motion was recorded, and flags the ones the camera protected itself. On-device vision names what moved — a person, a vehicle — so you skim a list instead of a timeline.
Scenario three · The adjuster

"Please send us the footage."

What they mean is: the date, the time, the location, the speed, a description of what happened — and a file they can open, that nobody has touched.

What most people send is a phone recording of a laptop screen, or a clip trimmed in iMovie. Both are worse than the original, and the second one invites a question you do not want asked.

You needThe camera's own file, byte for byte, not re-encoded.
AndA written account with the numbers already in it.
DriveReelExports the original clips untouched, plus a PDF carrying the route, the speeds, what happened and stills of the moments — so the email is one attachment and one link, not a paragraph of apology.
02

Card in. Answer out.

Five steps, and only the first one asks anything of you.
Step 01

A folder of strangers

Plug the card in. Thirty files for a half-hour drive, split across cameras, event clips filed somewhere else, every name a timestamp. This is what every dashcam hands you.

Step 02

Back into drives

Clips that run consecutively are chained into the journey they came from — across cameras, across event files, across the boundary where the interesting thing happened.

Step 03

What the car already knew

Position, speed and heading are embedded in the video by the camera itself, once a second. DriveReel reads them out of the file and draws the drive: where you slowed, where you turned, where something happened.

Step 04

Ask it a question

Street names you drove down. A shop you passed. What was said in the car. What the camera saw. Type a word and land on the second it happened.

Step 05

Something you can send

The original clips, untouched — plus a report with the route, the numbers, what happened and the stills. One attachment instead of an explanation.

Card · 196 files
…5000_D.MP4…5100_D.MP4 …5200_D.MP4…5300_E.MP4 …5400_D.MP4…5500_D.MP4 …5600_D.MP4…5700_D.MP4 …5800_P.MP4…5900_P.MP4 …6000_P.MP4…6100_P.MP4 196 files 29 GB · nothing named Home to the office 08:42 · 22 min · 9.1 mi · 30 clips Office to the school run 15:58 · 18 min · 7.4 mi · 24 clips Parked · Sainsbury's 19:04 – 04:31 · 412 motion fragments · 2 camera events The long way home 21:12 · 41 min · 26.8 mi · 44 clips 196 files → 4 drives WHITE VAN · 0.91 FRONT 0:00 18:02 7:41 · Braking −18 mph 9:02 · Left turn 87° 11:20 · Siren, 6s bollinger canyon The long way home 4:18 in · “…turned onto Bollinger Canyon Road…” Home to the office 11:02 in · street sign read from the picture Parked · Sainsbury's 19:41 · nearby place 3 records · speech, road signs and places Incident report Tuesday 1 September 2026 · 13:58 · San Ramon, CA DISTANCETOP SPEED HARD BRAKES 7.4 mi44 mph 2 07:41 BRAKING — 18 MPH LOST 09:02 LEFT TURN — 87° 11:20 SIREN HEARD — 6 SECONDS Originals attached · never re-encoded
What the card gives you
03

What it does, in full.

Five screens, and the reason each one exists.

Feature 01

Trips, not clips

Consecutive clips chain back into the journey they came from — across cameras, across event files, and across the boundary where the interesting thing happened. Grouping compares start to start, never end to start, so a clip truncated by a power cut doesn't split one drive into two.

The band along the top is six months of days. A day with footage is filled; an empty one is still drawn, because a gap in a dashcam archive is information and a day that quietly vanishes is not.

  • 126 days on one band
  • Drive / parking as a bar, never a truncated count
The library — what you have, and which days you have it for
Feature 02

The telemetry you already had

Cameras write GPS sentences inside the video once a second. DriveReel reads them straight out of the file — no sidecar, no account, no upload — and verifies every checksum, because compressed video contains byte sequences that look like GPS and aren't.

Four lanes on one clock: speed against the posted limit, force as a signed bar off centre, one tick per manoeuvre, and the clip boundaries underneath so you can see where the minutes break.

  • 1 Hz position, speed and heading
  • 0.30 g the threshold that counts as hard braking
  • Blue → amber → red, never green → red
A drive on four lanes — the colour carries meaning, and says so
Feature 03

Search what was seen and what was said

Streets you drove down, businesses you passed, text read off signs in the picture, and the words spoken in the car. Type what you'd actually say — white van, roundabout, the school — and land on the second it happened.

Every result says which it was. Seen is the camera. Said is the microphone. The app never blurs the two, because "a white van" in the picture and "a white van" in a sentence are different kinds of claim.

  • Every record searched at once, drives and parking
  • On your machine — the index never leaves it
One search, across everything you've ever recorded
Feature 04

A night of parking, in one screen

Parking is the mode that defeats every dashcam app. The engine is off, so the camera stops embedding GPS altogether, and nine hours collapse into four hundred motion fragments with nothing to tell them apart.

DriveReel draws the fragments where they actually fall in the night, so the gaps read as gaps, reads the place off the stamp burnt into the corner of the frame — and labels it as read from the picture, because a position from OCR deserves a different word from a position from a satellite — then describes each fragment in a sentence.

  • Nine hours of nothing, and the eleven minutes that aren't
  • One line each, so the right one is findable
Parked overnight — gaps drawn as gaps, each fragment described
Feature 05

Evidence that holds up

Two things leave the app. The camera's own file, copied byte for byte with its telemetry intact and a SHA-256 beside it — and a PDF carrying the route, the speed, the deceleration and the stills.

The original is never converted, trimmed, brightened or shrunk to fit an email. Every one of those is a modification, and a modification is the question you do not want an adjuster or a lawyer to ask.

  • Passthrough only — no re-encode on any export path
  • SHA-256 printed with the file it belongs to
The original, and the report that explains it

And the specifics underneath

Vehicles, people, plates

On-device vision marks what was in frame and when, at full resolution so a registration is legible rather than a smear.

What was said

Speech in the car is transcribed locally and indexed alongside everything else. Captions are off until you ask for them.

Every camera, on one clock

Front, rear and interior play against the same composition time, so switching angle never loses your place.

Unreadable is a state

A clip the app cannot parse is kept and reported by name. Nothing is dropped quietly to make a number look tidier.

It never deletes

Import copies off the card and leaves the card alone. Deciding what to erase stays a decision you make yourself.

Works with what you own

Any camera that writes standard files with embedded GPS. Where a manufacturer encrypts its own format, the app says so instead of guessing.

04

Why the original matters more than the clip.

“any modification, however benign, creates a chain of custody question” Nexar, on why dash cam footage gets rejected

This is the part most people get wrong, and it is the reason DriveReel is built the way it is. Trimming a clip to the exciting bit, brightening it, or re-encoding it to make it small enough to email are all reasonable instincts — and all of them hand the other side something to argue about.

OverwritingLoop recording eats the oldest footage continuously. Retrieve it late and the clip is simply gone.
Missing metadataFootage without a timestamp and position is harder to authenticate — it has to be shown to be from when and where it claims.
Selective clipsSending the ten seconds that help while the rest exists invites a completeness challenge.
Re-encodingEvery conversion is a modification, and modification is the question you do not want asked.

DriveReel's answer to all four: import off the card before the loop eats it, keep the embedded telemetry attached to the record, export the whole drive rather than a fragment, and never re-encode anything on the way out.

05

The desk does the work. The pocket does the moment.

Two apps, one library. The Mac holds the footage; the iPhone streams from it.
macOS — five lanes, an inspector and seventeen shortcuts
iPhone — one strip, and the list is the navigation

The lanes did not shrink; they moved. A 44-point list row is a good touch target and a 22-point lane tick is not, so on the phone the event list becomes the primary way of moving and the strip becomes a single shape you drag a thumb across — ticking the Taptic Engine at every event, which means you can find the four things that happened in a thirty-minute drive without looking at the screen.

  Mac iPhone
Import from the cardYesNo — a phone has no card slot
Holds the libraryYesStreams from the Mac
Browse every drive offlineYesYes — the list is tiny
Describe footageYes, at full resolutionFills the gaps the Mac hasn't reached
Pinch to read a plateNoYes
Build the PDF reportYesAsks the Mac to
Share the original fileYesYes — fetched from the Mac
Delete footageYesDeliberately not

The phone cannot delete footage on purpose. The Mac is the library of record, and a pocket device that can empty a bin it cannot see the contents of is a device that will eventually lose somebody's evidence.

06

Pricing.

Buy the Mac app once. The subscription only exists because the phone app has a Mac to keep talking to.
 

Free

$0
Forever. No account.
  • Import from any card or folder
  • Clips chained back into drives
  • Play, scrub, switch cameras
  • Route and speed from the embedded GPS
  • Unlimited footage — it's your disk
Download for Mac
Mac + iPhone

Pro

$6 / month
Or $59 a year. Cancel whenever.
  • Everything in Base
  • The iPhone app, streaming from your Mac
  • Evidence packages with file hashes
  • Batch export across a whole day
  • Parking review — a night in one screen
  • New apps from Minddrift included
Start Pro

DriveReel is in development and not yet on sale. These are the planned tiers — the buttons currently join the early-access list, and switch to real checkout at launch.

Everything, tier by tier
  Free Base Pro
Price$0$39 once$6 / month
Import from any card or folderYesYesYes
Clips chained back into drivesYesYesYes
Route and speed from embedded GPSYesYesYes
Play, scrub, switch camerasYesYesYes
Export originals, never re-encodedYesYesYes
Events — braking, acceleration, turnsYesYes
Search speech, road signs and placesYesYes
On-device vision — vehicles, people, platesYesYes
PDF incident reportsYesYes
Parking review — a night in one screenYes
The iPhone app, streaming from your MacYes
Evidence packages with file hashesYes
Batch export across a whole dayYes
New apps from Minddrift includedYes
Keeps working if we stopYesYesReverts to Base
07

Getting it.

Checkout

DriveReel Base — Mac

DriveReel Base · one-time licence$39.00
Estimated taxcalculated at checkout
Total$39.00
Join the early-access list
Visa Mastercard Amex Apple Pay PayPal

Payment is handled by the processor on their own page. Card details are never typed into minddrift.ai and never touch our servers.

Or from the App Store

The iPhone app ships through the App Store. The Mac app is sold direct, so a licence is a file you own rather than an account you keep.

macOS 13 or later, Apple silicon or Intel. The free version is the whole viewer — no trial clock, no watermark.

08

Reasonable questions.

Does my footage go to a server?
No. There is no account and no upload. Reading the telemetry, describing the picture, transcribing the audio and building the search index all happen on your own machine, using frameworks already installed on it. The iPhone app streams from your Mac over your own network — the footage never passes through us.
Which cameras work?
DriveReel reads the card, not the brand. Factory-fitted systems and aftermarket cameras both — Viofo, BlackVue, Nextbase, Thinkware, Garmin, 70mai and the long tail of white-label cameras that share their formats. A camera's layout is handled as a description rather than as code, so adding one is a row in a table rather than a release.
Will it re-encode my video?
Never on the way out. Exports are stream copies of the camera's own file. The iPhone app streams a smaller re-encoded proxy so that footage can move over a network at all — and it labels that proxy as a preview everywhere it appears, because sending a transcode to an insurer is the one mistake this app exists to prevent.
What if the camera encrypts its files?
Some do — Tesla began encrypting dashcam clips by default in recent firmware. DriveReel detects that from the file's first bytes and tells you what it found and how to unlock the clips in the car, rather than failing with an error that explains nothing.
Is a one-time purchase really one-time?
Yes. Base is a licence for the Mac app, bought once. Pro is a subscription because it includes the iPhone app and the service that keeps the two in step — and because a subscription that stops working when you stop paying should only ever cover something that costs money to run.

Be there when it ships.

We'll write once when the Mac app is ready, and once when the iPhone app follows. Nothing else.