AVIF Playback on Smart TVs via Network Shares

Smart television operating systems display mixed capabilities when handling AVIF (AV1 Image File Format) images over local network shares such as SMB, NFS, or DLNA/UPnP. Although AV1 hardware decoders are increasingly standard in modern smart TVs, the ability to render static AVIF images over a network depends on the TV operating system's software stack, the native media player's container support, and the network protocol serving the file. Consequently, while some modern platforms handle AVIF files without friction, others require transcoding media servers or third-party client applications to display them.

Hardware Decoding vs. Software Implementation

AVIF utilizes the compression algorithms of the AV1 video codec to deliver high-quality static images and image sequences at substantially lower file sizes than JPEG or PNG. Most 4K and 8K televisions released since 2020 include dedicated hardware AV1 decoders. However, hardware-level video decoding does not inherently grant still-image decoding. The television's operating system must explicitly integrate an AVIF image parser (such as libavif) into its image-rendering pipeline. Without this software layer, the native photo viewer will report the file as unsupported or corrupt, despite the hardware being technically capable of processing the underlying AV1 bitstream.

Operating System Support Over Network Shares

Android TV and Google TV

Android added system-level support for AVIF in Android 12. Devices running Android TV 12 or newer can natively parse AVIF files. However, the default media players pre-installed by TV manufacturers (such as Sony, Philips, or TCL) do not always index AVIF files when scanning network paths.

To overcome native software limitations, Android TV users have the advantage of robust third-party app stores. Applications such as Kodi, VLC for Android, and Nova Video Player include their own decoding libraries and network clients. These apps bypass native OS limitations, connecting directly to SMB or NFS shares to decode and render AVIF files reliably.

LG webOS

LG webOS models equipped with AV1-capable processors can process AV1 video streams, but native support for AVIF still images remains restricted. The default "Photos & Video" app in webOS primarily indexes traditional image formats like JPEG, PNG, and MPO. When accessing local shares via SMB or UPnP/DLNA, webOS typically ignores files with the .avif extension. Because webOS restricts sideloading and lacks third-party image viewers with internal AVIF parsers, native direct playback over local network shares on LG TVs is largely unavailable.

Samsung Tizen

Similar to webOS, Samsung's Tizen platform features AV1 hardware decoding on modern sets but maintains limited native support for AVIF still images within its default media player. Browsing an SMB or USB share via Tizen's built-in file manager usually results in unrecognized file errors for .avif containers. Tizen's app ecosystem does not currently feature broad third-party image viewers that bundle standalone AVIF decoders.

The Impact of Network Protocols: SMB vs. DLNA

The network protocol used to share images fundamentally changes how smart TVs process AVIF files:

• SMB and NFS (Direct File Access): When a TV accesses a file share via Server Message Block (SMB) or Network File System (NFS), it reads the raw file directly. In this scenario, playback success depends entirely on the TV client's internal software parser. If the app supports AVIF, the image loads; if not, it fails.
• DLNA and UPnP (Server-Mediated Streaming): DLNA relies on a server-client handshake where the server advertises media profiles using specific MIME types (e.g., image/avif). Most older DLNA servers do not recognize the AVIF MIME type and fail to serve the file altogether. Even if recognized, the DLNA client on the TV must declare to the server that it supports AVIF. If the TV does not declare this capability, the server will either hide the file or attempt to transcode it on the fly into a baseline JPEG.

Recommended Workarounds for Unsupported TVs

For smart TVs running webOS, Tizen, or older Android TV builds that cannot natively render AVIF files over network shares, two primary solutions exist:

1. Media Servers with On-the-Fly Transcoding: Running media servers like Plex, Jellyfin, or Emby on the host network allows AVIF files to be converted to compatible formats (such as JPEG or WebP) before they reach the television, preserving viewability without requiring manual batch conversion.
2. Dedicated External Streaming Devices: Using external streaming hardware running open platforms (such as an Apple TV 4K running tvOS 16+, or a modern Android TV streaming box) ensures broader codec and container support via specialized media apps, circumventing the native software bottlenecks of the TV panel itself.