BetaFPV VR04 HD FPV Goggles Review

The BetaFPV VR04 HD FPV Goggles are a budget, box-style goggle built around BetaFPV’s ArtLynk HD system. They are best known as the goggle that ships in the Aquila20 HD FPV Kit, but they are also sold separately. For now they are not really an optional purchase if you want to go down the ArtLynk route - at the time of writing they are the only goggle that supports BetaFPV’s HD system, so if you want to use it, you will need them.

The pair I am reviewing came as part of the Aquila20 HD kit, which was sent to me by BetaFPV for review.

Box-style goggles

The VR04 are a box-style goggle - a single screen behind a pair of lenses, rather than the two-screen layout you find in higher-end FPV goggles. Box goggles are bulkier and you will look like even more of a nerd than usual, but they have the advantage of being cheap and being easy on people who wear glasses.

For me the form factor is not an issue - I have been in the hobby long enough that I do not care how the goggles look. No matter how slick they are, you will still look like a nerd to anyone who is not into FPV.

Two versions: HD and HD Pro

Before you buy, be aware there are two versions of these goggles, and the difference is small but worth understanding:

VR04 HD - 2x 18650 2600mAh cells (~3 hours), $148.99
VR04 HD Pro - 2x 18650 3800mAh cells (~4 hours), adds live video streaming over the USB-C port via DisplayPort, $158.99

So for $10 more the Pro gets you bigger batteries and the ability to pipe the video out over USB-C - handy if you want to stream or feed the feed to a screen. Everything else (screen, optics, recording, the ArtLynk system itself) is identical between the two.

The battery upgrade isn’t really worth it - the goggle just uses 18650 cells, so you can just buy higher capacity after market cells and have the same result - the video streaming might be worth it though.

For the record, I am reviewing the regular VR04 HD - so the battery life and “no DisplayPort out” notes in this article are for that version.

In the box

There is not much to unpack: you get the goggle, the head strap with the battery case built into the back, and the two 18650 cells. The cells slot into that case on the back of the strap, and that is also where they charge from - straight over USB, so you do not need a separate charger.

Specifications


Type	Box-style HD FPV goggles
Video system	ArtLynk HD (BetaFPV) - digital only
Screen	4.5” LCD, 1920x1080
Recording	1080p@60fps DVR to microSD (FAT32)
Bitrate	8 / 16 / 24 Mbps selectable (4 Mbps in standby)
Output power	25 / 100 / 200mW selectable
Range	>400m
Power	2x 18650 (2600mAh included), or any 2-6S battery
Runtime	~3h standby / ~1.5h in actual use
Power port	USB Type-C on the battery holder; barrel plug to the goggle
Weight	~400g (without batteries)
Price	$148.99

Power

The goggles are powered by a 2S Li-Ion battery which is integrated into the head strap and connected to the goggle via a barrel plug. The power system is very flexible though - you can basically plug in any 2-6S battery.

The battery has its own power switch, which I am not really a big fan of. Since it is connected via a barrel plug, I would have preferred the goggle to just switch on once the battery is connected. The switch does not really have any upside for me - on the contrary, it is just one more component that could break. But I get it: this was a big topic on the FatSharks back then, so to avoid any backlash I guess it was necessary.

The included cells are rated at 2600mAh each. One thing that caught me out: out of the box the goggle simply switches off without any warning once the cells drop to around 3.2V - no beep, no on-screen warning, it just goes dark. There is a low-voltage alarm in the settings, but it appears to be disabled by default, so I would strongly recommend enabling it as one of the first things you do - otherwise you will eventually get surprised by an empty battery mid-flight - ask me how I know…

The Low Battery Alarm toggle (shown enabled here) lives under Settings → Device, alongside the output power, bitrate and a few other handy switches.

The upside is that the rating is honest: charging back up from that cut-off point put pretty much exactly 2600mAh back into each cell, so you really are getting the rated capacity out of them.

Do not read too much into the “~3 hours” figure though - that is a standby number. In actual use my effective runtime was closer to 1.5 hours, which is still plenty for a normal session, but if you are out for a longer one it is well worth bringing a spare set of 18650s to swap in.

Image quality

The screen is a 4.5” 1080p LCD, and for a box goggle in this price range it genuinely looks good - sharp, plenty bright and with colors that are perfectly pleasant to look at. You are not getting the pixel density of a high-end goggle pressed right up to your eyes, but in flight it is more than good enough and I never found myself wishing for more resolution.

The image you get is only as good as the ArtLynk feed feeding it, and I have covered the system itself in more detail in my ArtLynk article and the Aquila20 review: latency is higher than analog and higher than the current top-tier digital systems, but it is more than flyable and you adjust to it within a few packs.

You can also tweak the camera settings from the goggle, so the image is not completely fixed - you have some room to adjust it to your liking and to the lighting conditions you are flying in.

One thing I noticed is that the live image in the goggles looks a touch cleaner than what the DVR captures - though, as I keep saying, that might just be the smaller screen hiding flaws that a big monitor would reveal.

Optics

Do not expect any fancy optics here - there is no focus and no diopter adjustment. From what I can tell the optical path is a single LCD whose image is bounced off a mirror and through a lens to your eyes, which is a simple and cheap way to do it. It works, but if you rely on diopter correction in your goggles you are out of luck here and will have to wear your glasses inside the goggle (which the box form factor at least accommodates).

You do get brightness adjustment in the goggle’s own screen settings, so you can at least dial the image to your liking.

Fan and fogging

Box goggles have a reputation for fogging up - a single screen sealed in a box right in front of your warm face is basically a recipe for it. The VR04 sidesteps that with a built-in fan, and in my use it has never fogged up on me. So that classic box-goggle annoyance is one thing you do not have to worry about here.

Antennas

There are two antennas, one on each side of the goggle, and they fold up out of the way when you are not using them. So you are getting a basic diversity setup rather than a single antenna, which should help with reception as you move around.

The DVR

The goggles record straight to a microSD card with a single button. The flight clips in my Aquila20 review are straight off this DVR. The recordings are perfectly usable for reviewing a flight or finding a downed quad.

You can also set recording to auto-record, which I would recommend - that way it starts capturing as soon as you have a feed and you never have to remember to hit the record button (which is exactly the moment you forget when you actually crash and need the footage).

Interestingly the Rec Device is a selectable option set to “Goggles” - which lines up with my hunch from the OSD that recording on the air unit itself may become an option at some point. You will also want to format the SD card from this menu the first time, and as noted, prepare it on your computer first.

Even better, there is a playback mode right on the goggle, so you can replay your DVR footage without taking the SD card out. This is genuinely useful out in the field: crash into some tall grass, rewind the last few seconds in the goggle, and you can usually spot exactly where the quad went down.

Alongside each recording the goggles also save an .srt file - a subtitle sidecar that carries flight data like signal reception. Drop it next to the video in a player that supports subtitles (or parse it yourself) and you can overlay those stats on playback, which is handy for reviewing where your link started to struggle.

The goggles show you the remaining free space on the SD card in the OSD, which is a nice touch so you do not get caught out mid-session. Interestingly there is also an air-unit-with-SD-card symbol in the OSD - so I suspect recording on the air unit itself (rather than just the goggle) might become an option at some point down the line.

Something to note is that the goggles will only format the first partition of an SD card, so I would highly recommend preparing the SD card on your computer: a single partition, FAT32, is fine. BetaFPV rates the card slot for cards up to 1TB.

In regards to quality, I feel like the recording looks slightly worse than what you see in the goggles, but this could also just be placebo since the screen I am reviewing on is so much bigger. In any case - since you are recording on the goggles - you will also record any potential break-up. The recording does not compare to an external action cam, but for what it is, it does the job really well - I don’t have any complaints.

The usual SD card caveats apply: use a good quality SD card with decent write speeds.

The menu is navigated with a 5 position joystick: up, down, left, right and push to enter, a back button and a dedicated recording on/off button.

Here there is not really much to complain about, the input works well enough and the menu navigation is quite intuitive. You enter the menu by short pressing the joystick.

The menu is split into Channel, Settings and Playback, and the status bar along the bottom is worth a look in its own right: it shows your channel, the air unit and goggle battery voltages, the current bitrate, distance, link status and the SD card free space - all at a glance.

Binding

If you bought the goggle as part of the Aquila20 kit, it comes already bound and you can skip this entirely. If you are pairing the goggle to a fresh air unit - or you just updated the firmware, which clears the binding - you will need to bind them.

Both the goggle and the air unit have a bind button, and the procedure is driven by audible beeps:

Power on both the goggle and the air unit
The goggle’s bind button is recessed - you need a long thin object like a needle to press it. Once you do, the goggle starts beeping to indicate it is in bind mode
Now long-press the bind button on the air unit (this one is easily accessible, no needle required) and wait for the confirmation beep - that tells you the two have paired

Interestingly, binding worked for me even though the goggle and the air unit were on different firmware versions - both were v1.x, mind you, so this is not me crossing the V1/V2 line. So minor version differences within the same major version seem to bind fine; it is the V1-to-V2 jump that actually breaks compatibility.

Just remember that a firmware update breaks the binding, so re-binding is part of the update routine.

You can have multiple quads bound to the same goggle and it will automatically pick up the active quad.

Comfort and fit

This is where the VR04 and I really did not get along.

The top strap is useless for my head - I ended up cutting it off. The strap, not my head.
The battery sits on the back of your head. With this goggle you do not get a choice in the matter, and I am not a fan of having the weight back there and on my head.
The foam is too thin and the fit just does not match my face. My face must be so far outside whatever BetaFPV designed against that I almost feel like crying. I can position it so that it is usable, but a thicker foam would have transformed the experience.

There is a glimmer of hope on the fit front though: the face foam is velcroed on, not glued. That means it is replaceable, so there is a real chance we will see thicker or differently-shaped foams down the line - whether from BetaFPV themselves or the aftermarket - that could fix the fit for faces like mine. Even a DIY thicker pad would be an easy mod given how it attaches.

What actually turned the fit around for me was ditching the stock setup: I swapped the head strap for an Ethix V3 strap and moved to a separate (custom) battery instead of the one built into the stock strap. The Ethix strap is wider, lets me put more even pressure on the goggle and - crucially - keeps it planted on my face instead of sliding around. Taking the battery off the back of my head at the same time solves the weight-at-the-back complaint too. Between those two changes the VR04 went from “I have to fight it into a usable position” to genuinely comfortable, so if the stock fit is not working for you, that is the first thing I would try before giving up on them.

For a goggle that comes bundled in a kit at this price point, I still think it is acceptable - you are not paying flagship money. But as a standalone purchase, the fit is the thing I would want you to try before committing.

I provided all of this feedback to BetaFPV, they listened and assured me they would forward it to their product development team. I hope that translates into actual changes in the next iteration.

Odds and ends

A few smaller things that did not warrant their own section:

Boot time is quick - around 5 seconds from power-on to a live image, which is about as good as it gets.
There is no audio - no headphone jack, no speaker, and no sound recorded to the DVR. Not a surprise on a digital system at this price, but worth knowing if you were hoping for it.
No head tracking - if you were hoping to use these for anything in that department, they do not do it.

Channels and flying with others

This is one to be aware of if you fly in a group. By default the ArtLynk system exposes 3 channels - so out of the box you can have at most three HD pilots in the air at once. There is more to it though: under Settings → Device → Mode you can switch the goggle into race mode, and that opens up 16 channels to choose from. So the three-channel limit is really just the default mode, not a hard ceiling - if you want to fly with a bigger group, race mode is the answer.

Each digital channel is wide and occupies a big chunk of spectrum, so coexisting with analog pilots nearby is messier than just swapping between neighbouring analog channels - but among ArtLynk pilots themselves, 16 channels is plenty for all but the largest meet-ups.

The output power is also adjustable between 25, 100 and 200mW, which helps here too: drop the power down when you are flying close to others to keep interference in check, and crank it up when you want more range.

As for a spectator mode - the kind of thing where a buddy puts on a second pair of goggles and tunes in to watch your feed, like you can on analog - there does not appear to be one. I could not find any way to bind a second VR04 to a flying pilot’s air unit. The only “share your view” feature is on the VR04 HD Pro, which can output its video over the USB-C port via DisplayPort to an external screen - but that is a wired connection to a monitor, not a wireless audience mode.

Analog compatibility

Unfortunately there is no built-in analog compatibility, and for this price point I can’t really say I’d expect it.

There is also no AV input of any kind, so you can not plug in a third party analog 5.8GHz receiver module the way you can with many other box goggles - the VR04 only accepts the digital ArtLynk feed from a compatible air unit. If you have a fleet of analog quads, these will not replace your analog goggles.

The one bit of forward-looking good news: BetaFPV is working on making ArtLynk cross-compatible with other Artosyn-based digital systems via firmware updates. So down the line the goggle may talk to more than just BetaFPV’s own air units - but to be clear, that is about other digital systems, not analog.

Updating

Updating is done entirely via SD card - no configurator and no USB cable needed. The whole thing runs through the goggles: you put both firmware files on the goggle’s SD card and the goggle handles the rest, pushing the air unit firmware to the quad over the wireless link. You can not flash the air unit on its own.

One thing that caught me out: the copter (air unit) gets upgraded first, and only then does the goggle upgrade. Updating just the goggle on its own does not appear to be an option - it always does the air unit first. So both firmware files need to be on the card, and you should make sure both devices are fully charged before you start, since you do not want either of them dying mid-flash.

Check what you are on first: Setting → System → Device Info. The two entries that matter here are Goggles Firmware Version and Drone Firmware Version (the air unit) - these are the ones you want to keep in sync
Download both the goggle and the air unit firmware from BetaFPV’s support page (linked under Resources below)
Copy both firmware files onto the SD card and insert it into the goggles
Power on both the goggles and the air unit and make sure they are connected (you can see the camera image in the goggles)
In the goggle menu, navigate to Setting → System → Upgrade → Start. Note that this is a manual step - simply restarting the goggle does not kick off the flash
The air unit is flashed first, the goggle second. Wait for it to finish - do not power anything off mid-update - then restart both devices, re-bind them, and check Device Info again to confirm both versions actually changed

A couple of gotchas worth knowing:

The filename matters. The goggle validates the firmware by its filename (something like P1_GND_VR04_v2.0.7_20260122_09de6e7.img) and expects a newer version than what is installed. If it already has that version it will simply skip the flash - which is exactly what happened to me: the copter updated, the goggle did not flash again because it was already on the matching version. That is expected, not an error. If you ever do need to force a re-flash or go back to an older version, renaming the file to a higher version number is the known workaround.
The goggle and air unit firmware have to match. A V2 goggle will not talk to a V1 air unit, and vice versa - so keep both on the matching version. If a jump from very old firmware fails with a “no image file found” error, flash an intermediate version first.

Under the hood: root access over USB

Like most of the modern digital systems, the VR04 is really a little Linux computer - it runs an Artosyn SoC (the “proxima-9311”) on a 4.9 kernel, and the whole ArtLynk stack is just userspace on top of that. What surprised me is how little stands between you and a root shell: out of the box, the goggle exposes a root SSH server over its USB-C port, no case-opening, soldering or secret button combo required.

When you plug the goggle into a computer it comes up as a USB network adapter (RNDIS). The goggle sits at 192.168.3.100, runs an (old) Dropbear SSH server on port 22, and the root account is enabled with a password that is the same across units. Give your machine an address on the same subnet and SSH straight in:

# 1) plug the goggle's USB-C into your PC, then find the new network interface
ip -br addr | grep enx          # e.g. enx46aaa7c842d5 on Linux

# 2) put your PC on the goggle's subnet (the goggle is 192.168.3.100)
sudo ip addr add 192.168.3.222/24 dev enx46aaa7c842d5
sudo ip link set enx46aaa7c842d5 up

# 3) SSH in as root - password is "artosyn"
#    the legacy flags are needed because the goggle ships an old Dropbear
ssh -o HostKeyAlgorithms=+ssh-rsa,ssh-dss \
    -o KexAlgorithms=+diffie-hellman-group1-sha1,diffie-hellman-group14-sha1 \
    -o Ciphers=+aes128-cbc,3des-cbc \
    root@192.168.3.100

That drops you at a root@art_sirius prompt with full run of the system - the same Linux that is decoding your video, driving the screen and recording to the SD card. From here you can poke around the init scripts under /etc/init.d, watch the ArtLynk processes, read the camera/RF config in /factory, and generally see how the whole thing is wired together. If you want password-less access, drop your public key into /root/.ssh/authorized_keys.

A few honest caveats:

This is undocumented and unsupported. It is not a feature BetaFPV advertises, and a future firmware update could lock it down, move the IP, or change the password. It worked on the v1.x firmware I tested; treat it as “true today” rather than a guarantee.
There is no safety net. Root means root - it is trivial to brick the goggle by changing the wrong file. Poke around read-only first, and do not write to the flash partitions unless you know exactly what you are doing.12

I went a much harder route to discover this - tapping the board’s debug UART (which, fun detail, runs at an awkward 1,152,000 baud) to read the boot logs - before realising the SSH server was sitting there in plain sight the whole time on an IP I had not thought to scan. If you just want a shell, skip the soldering iron: the USB route above is all you need.

Resources

Conclusion

Before the wrap-up, the short version:

Pros

Digital HD image at an analog-box-goggle price
Capable DVR: 1080p60, auto-record, in-goggle playback, and an .srt telemetry sidecar
Built-in fan - never fogged up on me
Two foldable diversity antennas
Selectable bitrate and 25/100/200mW output power, plus a 16-channel race mode
Honest battery rating, and the cells are standard 18650s you can swap or upgrade
Surprisingly hackable - a root shell over USB out of the box
Replaceable (velcroed) face foam leaves the door open for a better-fitting pad

Cons

Stock fit was poor for me - thin foam, head-mounted battery, useless top strap (an Ethix strap + separate battery fixed it)
No focus and no diopter adjustment - glasses-only if you need correction
Low-voltage alarm is disabled by default; without it the goggle just dies at ~3.2V with no warning
Effective runtime is more like 1.5 hours than the headline ~3
No audio, no head tracking
No analog or AV input, and no wireless spectator mode

The conclusion here is a bit difficult, since if you want to use the ArtLynk system, this is your only way of using it - at least for now. My hopes are still up that this will become a system supported by all manufacturers in the space, so that we can in the future look at Skyzone goggle alternatives, for example, or external receivers that plug into existing goggles.

For what they are, they are OK. There is a lot of potential for improvement, but they are definitely usable for their intended purpose.

And at $148.99 it is hard to be too harsh: that is roughly what you used to pay for a “better” analog box goggle, except here you are getting a digital HD image for the money. If you are buying into ArtLynk anyway - or you got them as part of the Aquila20 kit - they do the job. Just try the fit if you can, and if you have the choice, the Pro is only $10 more for bigger batteries and DisplayPort out.

Chris is a Vienna based software developer. In his spare time he enjoys reviewing tech gear, ripping quads of all sizes and making stuff.

Learn more about Chris, the gear he uses and follow him on social media:

Also check out

ArtLynk HD System

Aquila20 HD Kit

LiteRadio 4