HDZERO
Last updated
Was this helpful?
Last updated
Was this helpful?
HDZero differs from other HD video solutions in the chipsets used to overlay OSD onto received video. The chipset that is used does not support alpha channel required for transparency of OSD elements. This means that a specific colour (127,127,127) in a font file is used to represent transparent pixels when the glyph is rendered onto the video when displayed. As such, the supported format is bitmap (bmp) 24 bit (8bit per RGB channel), for OSD font images.
Due to the lack of alpha channel (transparency) support, OSD glyphs have a hard edge and appear harsher than other HD systems. Additionally when creating a font file for the OSD, the creator of the file needs to be aware of the specific colour RGB value used for transparency.
HDZero supports 720p by default as well as 1080p and 540p resolutions. Both 720p and 540p use the same font file that is 720p (24x36 glyph size) as the 540p resolution is upscaled and displayed in the goggles as 720p, prior to OSD overlay. The 1080p font file uses 36x54 glyph size.
All font files for HDZero use a glyph arrangement of 16 glyph columns wide and either 16 or 32 glyph rows depending on the flight controller firmware requirements.
Font naming must be adhered to so that the correct font and resolution is selected when displaying the OSD. e.g. BTFL_000.bmp for 720p/540p and BTFL_FHD_000.bmp for 1080p resolution.
As there is support for various flight controller firmwares, there is a [4 character] flight controller ID also required within the font naming so that the correct font is used for the connected flight controller.
BTFL = Betaflight
INAV = INAV
ARDU = Ardupilot
QUIC = Quicksilver
EMUF = Emuflight
The font files for community created OSD are stored on the SD card within /resource/OSD/FC/.
Community fonts can be found at
SNEAKY_FPV fonts for HDZero can be found at