dashcamigo - free dashcam viewer that runs in the browser

dashcamigo

New Member
App Developer
Joined
May 10, 2026
Messages
13
Reaction score
6
Location
Almaty
Country
Kazakhstan
Hey everyone!

I built dashcamigo — a free, browser-based viewer and editor for dashcam footage.

App: https://dashcamigo.app

Source: https://github.com/amkulikov/dashcamigo

app-desktop-1240.webp


You just point it at your SD card folder, and it processes everything locally in your browser. Nothing gets uploaded to the cloud — the network is only used for map tiles (and optional analytics/crash reports you can turn off).

What it can do:
  • Continuous playback: Automatically stitches those fragmented 1–3 minute clips into complete trips based on timestamps.
  • Map & telemetry charts: Displays your route color-coded by speed, alongside a G-force chart that highlights hard braking or impacts.
  • Multi-camera sync: Synchronizes front, rear, and cabin feeds on a single timeline. You can expand any angle with one click.
  • Flexible export: Combine multiple camera angles into one MP4 (side-by-side, grid, PiP), burn in telemetry (speedometer, G-force, mini-map), crop, or adjust playback speed. Exports GPS to embedded MP4 data or standalone .gpx.
  • Plate & face blurring: Blur sensitive areas manually or use browser-based AI auto-detection (powered by ONNX) that tracks objects across frames.
  • Wide format support: Handles .mp4, .mov, .ts, .m2ts, .mkv and parses embedded/sidecar GPS data from 70mai, VIOFO, BlackVue, Vantrue, Garmin, GoPro, Nextbase, and others.
  • Works offline: Can be installed as a PWA and run completely offline after your first visit.
If your camera model isn't recognized, you can send a quick sample report directly through the app to get it added: https://dashcamigo.app/add-my-camera

I’m the developer, so if it chokes on your footage or crashes, drop a comment here or open an issue on GitHub.

Alex
 
Last edited:
Small update since the first post.

Performance. Big pass on the parsing and playback path. Large cards with hundreds of clips don't choke anymore - trips build faster, scrubbing is smoother, and front/rear sync holds up on long timelines. Lighter on weaker machines too.

More cameras. Added support for more models.

Export overlays. The main one. You can now burn overlays straight into the exported clip or frame - route map, speed, GPS coordinates, date/time and G-sensor. Mix and match what you want and tweak how it looks, then export.

Still here: https://dashcamigo.app

If your camera isn't recognized, send a short sample to feedback@dashcamigo.app and I'll add support. Bug reports and feature requests welcome here too.
 
Hi everyone, a quick update!
  • Added support for dozens of new dashcam models.
  • Added a dedicated page with clear instructions on how to help get your specific model supported: https://dashcamigo.app/add-my-camera
  • Better Export UX: Polished the export flow so it’s much smoother and more intuitive now.

As always, feedback and bug reports are welcome!
 
Another update!
  • Added support for another batch of dashcam models.
  • Reworked parking mode support - parking clips are now handled properly on the timeline.
  • Added blur zones on export - you can mask out areas of the frame, including tracking a selected object so the blur follows it.
  • Added experimental automatic face and license plate blurring on export. It's still on the slow side and not always accurate, but as with everything else - it all runs in your browser, nothing leaves your machine.
As always, feedback and bug reports are welcome!
 
Is it possible to export the GPS track layer video separately so I can use it in other video editing software?
 
Is it possible to export the GPS track layer video separately so I can use it in other video editing software?
Currently, this isn't possible. I'll look into whether it can be added without too much hassle.

As a workaround for now: maximize the map size during export, and then simply crop the final video in your editing software so only the map is left.

Quick question though: what exactly are you missing in the built-in export editor?
 
Currently, this isn't possible. I'll look into whether it can be added without too much hassle.

As a workaround for now: maximize the map size during export, and then simply crop the final video in your editing software so only the map is left.

Quick question though: what exactly are you missing in the built-in export editor?
Your dashcam viewer interface is excellent, but even at the highest quality, the exported video quality is somewhat poor. It would be better if the bitrate could be set manually. Also, the dashcamigo.app watermark cannot be turned off.
 
Your dashcam viewer interface is excellent, but even at the highest quality, the exported video quality is somewhat poor. It would be better if the bitrate could be set manually. Also, the dashcamigo.app watermark cannot be turned off.
Thanks for the feedback! I'll be working on improvements in this area very soon.

If you have any other suggestions or catch any issues, definitely let me know.
 
Your dashcam viewer interface is excellent, but even at the highest quality, the exported video quality is somewhat poor. It would be better if the bitrate could be set manually. Also, the dashcamigo.app watermark cannot be turned off.
Just a quick update: the option to disable the watermark is now available.

Also fixed a bug messing with the export quality at 4K/60fps. The quality selection has been reworked, and the requested manual bitrate setting is added too. Everything looks perfect on the test samples now, but if the issue is still there, just send over your files.

It's already live on the beta version:
 
Just a quick update: the option to disable the watermark is now available.

Also fixed a bug messing with the export quality at 4K/60fps. The quality selection has been reworked, and the requested manual bitrate setting is added too. Everything looks perfect on the test samples now, but if the issue is still there, just send over your files.

It's already live on the beta version:
The problem has indeed been resolved. Furthermore, it would be even better if you could improve graphics card utilization and increase output speed.
Currently, the graphics card encoding/decoding utilization rate is around 60%. My graphics card is an RTX 4060 Ti.
 
Hello, the newly released beta version has resolved the time display error and improved export speed.
Furthermore, I've found that when exporting at the same bitrate, the video quality exported using Mediabunny codec is even better than that exported using some editing software.It's very close to the original video quality.
 
Hello, I'm here to report another problem. When I export a large video file, The video is approximately 1 hour long.,after exporting about 15GB, the memory is used up, and then the export fails with an error.
QQ20260730-173411.webp
QQ20260730-173843.webp
 
Hello, I'm here to report another problem. When I export a large video file, The video is approximately 1 hour long.,after exporting about 15GB, the memory is used up, and then the export fails with an error.
Which browser are you using?
 

Tried reproducing this, but no luck so far. Not really sure what's causing it — in Chrome, RAM usage shouldn't be tied to the video length.
Could you try triggering the error again, preferably on the beta version? Once it fails, just hit any "Report a problem" button, follow the steps to download the .txt report file, and send it over.

1785424644209.webp
 
The reason has been found: the map is not displayed because there is no GPS data for the first few tens of seconds.
Checked the logs - looks like the issue happened during the reading process, which could be caused by a few different things.

I've tweaked the logic to make the export less likely to crash from one-off read errors. The fix is already live on the beta.

If it still fails, try exporting a small chunk right around 33:00-36:30. It's possible there's an issue with specific sectors on the disk/SD card.

Also, good catch about the map not showing up! I’ve been meaning to add a placeholder for when GPS data is missing, and it's finally done.
 
Checked the logs - looks like the issue happened during the reading process, which could be caused by a few different things.

I've tweaked the logic to make the export less likely to crash from one-off read errors. The fix is already live on the beta.

If it still fails, try exporting a small chunk right around 33:00-36:30. It's possible there's an issue with specific sectors on the disk/SD card.

Also, good catch about the map not showing up! I’ve been meaning to add a placeholder for when GPS data is missing, and it's finally done.
After testing, the export of very large videos was successful, and memory usage was normal.
 
Back
Top