Version 5.5.3: every camera on its own card – BlackVue and VIOFO side by side.
Dashcam Downloader (formerly BlackVue Downloader) · Microsoft Store app for Windows

What’s changed from 5.1.1 to 5.5.3

A new main window, VIOFO cameras, and more accurate speed and G-force figures. If you are on 5.1.1, everything on this page arrives with the 5.5.3 update.

Get Dashcam Downloader – free 7-day trial

Microsoft Store · Windows 10 and 11 · fully working trial

The short version

Version 5.5.3

A new name: Dashcam Downloader, and every camera at a glance

ChangedNew name and icon

Blackvue Downloader is now Dashcam Downloader, with a new icon and a new title. It is the same app on the same Microsoft Store page with the same licence; cameras, settings, logs and downloads carry straight over.

NewEvery camera at a glance

ChangedDownload by date

Redone in the new style, like Add / Edit camera: the camera, then Recordings between with a date, hour and minute for From and To. It sizes itself to the screen at any display scaling (the old window was cut off).

Fixed

Version 5.5.2

The app's independence stated in the app

ChangedIndependence

The main window and About stated that the app is independent and not made by or affiliated with BlackVue / Pittasoft or VIOFO (Microsoft Store certification). From 5.5.3 this is in About and the Store description.

Version 5.5.1

Card animations after the tray, and Process GPS progress

Fixed

NewProcess GPS data progress on the card

Parsing GPS tracks · 1,234 of 17,483 (7%) with the card's fill growing to match, then saving day tracks · 5 of 15. Each .gps file is now read once (5.5 read it twice), which matters on a network or USB drive.

Version 5.5

VIOFO cameras, a new look, Find cameras, and more accurate speed and G-force figures

NewVIOFO cameras

BlackVue Downloader now downloads from VIOFO dash cameras as well as BlackVue - side by side in the one app. VIOFO support is included for everyone; there is no add-on.

NewFind cameras

Find cameras... on the Add / Edit camera window looks for BlackVue and VIOFO cameras on this PC's network and fills in the IP address (and the name, if none has been typed). Read-only and quiet: a short connection test on ports 80 / 443 across this PC's own network(s) (adapters with a gateway only), then the app's usual identification requests only where something answers. Nothing is changed on any device.

NewSet-up tips for BlackVue and VIOFO cameras

in About, on the Add / Edit camera window, and on the first page of each camera's Overview: joining the home Wi-Fi, a fixed IP address, power while parked, and (VIOFO) station mode and Wi-Fi in parking mode.

Newmodern main window

A new main window with a card for each camera. The original window is kept: About > Settings > Classic layout (takes effect at the next start). The modern window opens unless Classic layout is ticked, and the classic one opens instead if the modern one cannot.

NewAdd / Edit camera window

Redesigned in the same style as the new main window (both layouts), light or dark as above.

Clip player: plays on into the next clip in time, from the same lens, until you stop it; Page Up / Page Down step a clip at a time.

Camera pictures for the DR770X (1CH, 2CH, Box) and DR590X; a DR770X used to show a blank tile. Pictures are matched on the model number whatever the spelling (900X2, DR900X-2CH Plus...), and the BlackVue pictures were updated.

Changes

Internal notes (for developers)
  • New: VIOFO - App.Novatek.cs (interface, read-only command list), App.ViofoAccess.cs, NovatekGps.cs, ClipName.cs (the one place that reads clip file names, BlackVue and VIOFO), ViofoSettings.cs + ViofoSettings.json; App.Finder.cs (Find cameras); SetupTips.cs; TitleMorph.cs + Icons\TitleMorph.
  • New: modern UI - ModernMainWindow.xaml(.cs), CameraActions.cs (every camera action, shared by both main windows), WindowTheme.cs (light / dark for the other windows), PacmanSplash.cs + Icons\Splash (250 frames).
  • New dependencies: WPF-UI and WPF-UI.Abstractions 4.3.0 (MIT; .NET Framework 4.8 unchanged), System.Memory 4.6.3 with System.Buffers 4.6.1, System.Numerics.Vectors 4.6.1 and System.Runtime.CompilerServices.Unsafe 6.1.2; App.config binding redirects set to the versions shipped.
  • New settings: classicLayout, splashShownFor, cameraOrder (camera IDs, display order only - the camera list itself, which the camera threads index by position, is never reordered), gforceMethod (once-only G-force recalculation), viofoIntroShown.
  • Licence state: trialStatus.licenceFailed (a check finished without confirming); errorChecking is now cleared only after the trial flags are set.
  • Speed: ParseGPS.ReadSpeedSamples / TrustedSpeed / TrustedPeak shared by parseGPSspeedonly, PeakSpeed and parseGPStrack.

Version 5.4

Track Data: each day's drives on a speed graph and a street map

NewTrack Data column in Drive Analytics

A fifth column (far right) lists each day that has a GPS track file, newest first, in the same style as the other columns: rank, distance (red), date and number of drives, then a green line with the driving time and top speed - click it to open that day's Track window. The window is wider to fit it (1900, reduced to fit smaller screens).

NewTrack window - the day's speed graph and the route on a street map, linked together

Google Earth: the earlier plan to open the day file in Google Earth on the web was dropped. Earth on the web cannot open a local file from a link (the user has to find and upload it each time), and it has no speed profile - that is only in Google Earth Pro, which still opens the same KMZ files as before.

Fixes

Internal notes (for developers)
  • New: TrackDay.cs (day KMZ reader: drives, distance, moving time, top speed, speed bands, clip index), TrackDayWindow.xaml(.cs), TrackMap.cs (route-only fallback map), Map\map.html.
  • New dependencies: Microsoft.Web.WebView2 1.0.4191.47 (NuGet, packages.config + build targets; WebView2Loader.dll in runtimes\win-x64\native) and MapLibre GL JS 5.24.0 (BSD-3-Clause; maplibre-gl.js/.css and its licence bundled in the Map folder - the last single-file build; 6.x is ES-modules only). Street map tiles: OpenFreeMap (free, no key, commercial use allowed). The Store package layout was checked to contain the Map folder and the WebView2 files.
  • OpenStreetMap's own tile servers (tile.openstreetmap.org) refuse the app: every non-browser request gets HTTP 200 with an Access blocked picture and an x-blocked header (any User-Agent/Accept/Referer; browsers on the same PC are fine; seen 2026-10-10). They are not used.
  • The map page is served from the app's Map folder through a WebView2 virtual host (bvd-map.example); navigation away from it is blocked and links (map credits) open in the user's browser. WebView2 data folder: the documented default for the Store install; LocalAppData\BlackVueDownloader\WebView2 when run unpackaged.
  • The Track window does not use AllowsTransparency (WebView2 cannot draw in a transparent window); WindowChrome keeps the frameless look and resizing.
  • Hardening: every handler guarded; WebView2 disposed outside its own events; hovering never touches the disk (a Record folder on a network share could otherwise freeze the window) - a clip's presence is checked on click; the map counts as ready once its style has loaded (single tile failures are not fatal, 20 s limit); no-route days and closing during map start-up handled.

Version 5.3

New BlackVue firmware, Camera settings and the Health check

NewWi-Fi passwords page in the Overview window

Shows your own saved passwords read from the camera - the camera's own hotspot password and the home Wi-Fi networks it connects to - so you can recover one you have forgotten (like Windows' show Wi-Fi password). They are decoded only on screen; the stored settings keep only the camera's encrypted form, and passwords are never written to the log.

NewCamera settings in the Overview window

The Overview now shows the camera's own settings as last read from it (kept while the camera is offline): time zone and daylight saving, how the clock is set (GPS / manual), the camera's clock compared with this PC (judged from its newest clip), recording options (audio, parking mode, quality and codec codes, stamps, speed unit, lock-event, sensor sensitivities), power (low-voltage cut-off incl. 24 V, scheduled reboot, Bluetooth) and Wi-Fi (the camera's own hotspot name, band, the Wi-Fi networks it joins, Cloud on/off where the model reports it, when the settings were last changed), indicators and sensors (LEDs, proximity sensor, GPS, image flip), voice prompts (volume, which prompts are on) and firmware details (version, language, config version, revision, image-sensor versions). Settings a model does not report are left out. Passwords are never read or stored.

NewAll Clips column in Drive Analytics

A fourth column lists every recording in the chosen time frame, newest first, under a heading for each day, in the same style as the other columns: type and date/time, then the full front and rear file names (green if the file is there, red if missing) - click to play. The window is a quarter wider to fit it.

Compatible with new BlackVue firmware (ELITE 10 v1.009, ELITE 8 v1.013, DR970X v1.014, ELITE 9 v1.010).

(Internal: the updated interface is the IMSL/CivetWeb API, as opposed to the legacy Boa/CGI interface. Verified endpoint by endpoint on a live ELITE 10 v1.009.)

New firmware (ELITE 10 v1.009 and other cameras on the IMSL/CivetWeb API)

New startup summary: a short title at startup, then - once the cameras have had their first check - one line per camera (online / away, last download, Health check result), free space on each save drive, the transfer mode, and a tip about a feature.

Fixes

Version 5.2.1

Fixes for one download at a time

Fixes

Version 5.2

One download at a time per Wi-Fi group, and the Camera Overview

NewOne download at a time per Wi-Fi group (transfer scheduler)

BlackVue cameras are single-antenna (1x1) Wi-Fi clients. When two of them download at once through the same access point they talk over each other - each camera can hear the AP but not the other camera - and the radio spends most of its time on collisions and retries. Two cameras downloading together are SLOWER in total than one after the other.

NewCamera Overview window

A new Overview button on each camera's Details tab (where Delete Camera used to be) shows that camera's lifetime figures, kept since the camera was added to this version (or since you last pressed Reset):

Changes