The Rockchip RK3399 was released in 2016, which should make it ancient by ARM processor standards. It uses a 28 nm process, has only two high-performance CPU cores, and predates the current habit of adding an NPU to practically every embedded processor. Yet RK3399 boards are still being manufactured, sold, documented, and used in commercial products.
You can now buy Rockchip processors with better power efficiency, faster graphics, and dedicated AI acceleration. Some of them don’t even cost more. But the RK3399 has something newer chips cannot immediately reproduce: almost a decade of hardware designs, Linux development, community fixes, and deployed products.
That history doesn’t automatically make the RK3399 a good choice in 2026. It does make it more difficult to dismiss than its age suggests.
Rockchip RK3399 Specifications
Rockchip took a different approach with the RK3399 than it did with many of its lower-cost processors. Instead of using four or eight identical efficiency cores, the company combined two Cortex-A72 performance cores with four smaller Cortex-A53 cores.
| Component | Rockchip RK3399 |
| CPU | 2× Cortex-A72 and 4× Cortex-A53 |
| Maximum CPU speed | 1.8 GHz for Cortex-A72; 1.4 GHz for Cortex-A53 |
| CPU architecture | 64-bit Armv8-A |
| Manufacturing process | 28 nm |
| GPU | Mali-T860 MP4 |
| Memory | Dual-channel DDR3, DDR3L, LPDDR3, or LPDDR4 |
| Video decoding | 4K H.265, H.264, and VP9 |
| Video encoding | H.264 up to 1080p |
| Display interfaces | HDMI 2.0a, DisplayPort 1.2, eDP, and MIPI DSI |
| Camera interfaces | Dual MIPI CSI with integrated ISP |
| Storage | eMMC 5.1, SD, SDIO, and SPI flash |
| Expansion | PCIe 2.1, USB 3.0, USB 2.0, and Gigabit Ethernet |
| NPU | None |
This was an unusually complete specification for a non-smartphone ARM processor in 2016. PCIe, USB 3.0, dual-channel LPDDR4, HDMI 2.0, and DisplayPort gave manufacturers enough flexibility to build laptops, development boards, media systems, and industrial computers around the same chip. There is one qualification to practically every RK3399 specification, however: the board still has to expose it. A processor supporting PCIe or DisplayPort doesn’t help when the manufacturer leaves that interface disconnected.
Two Fast Cores Were a Good Decision
The RK3399’s CPU layout is probably the main reason it aged as well as it did. Its four Cortex-A53 cores aren’t particularly interesting today: they’re useful for background services and parallel workloads, but processors built entirely around Cortex-A53 cores rarely make responsive desktop computers. The two Cortex-A72 cores are different. They provide considerably stronger single-threaded performance, which helps with web browsing, software installation, code compilation, and the many short tasks that determine how responsive a Linux system feels.
This also makes comparisons with newer processors less straightforward than they first appear. The RK3566 has four more modern Cortex-A55 cores and uses a more efficient 22 nm process, but it has no large performance cores. As a result, the RK3399 can still perform surprisingly well in lightly threaded workloads. It isn’t faster overall, however: only two Cortex-A72 cores are available, and that becomes an obvious limitation when an application can keep several cores busy.
The 28 nm process also means more heat. A small heatsink may be sufficient for light use, but sustained compilation, rendering, or CPU stress can require a larger heatsink or a fan to prevent throttling. This is where the RK3566 low-power architecture makes more sense—it gives up the RK3399’s stronger burst performance but is easier to cool inside compact devices.
The GPU Shows Its Age
If the CPU is the pleasant surprise, the Mali-T860 MP4 is the part that most clearly dates the RK3399. It was reasonably capable when the chip appeared and could handle Android interfaces, desktop composition, lightweight 3D applications, and older games. Rockchip also advertised support for OpenGL ES 3.1 and OpenCL, giving manufacturers more options than they had with the GPUs used in cheaper ARM processors at the time.
Compared with current Rockchip GPUs, though, the Mali-T860 is slow. The Mali-G52 used in processors such as the RK3566 and RK3576 belongs to a newer generation, while the Mali-G610 MP4 inside the RK3588 is in an entirely different performance class. Basic desktop rendering and 4K video playback aren’t necessarily a problem, but gaming, advanced emulation, and GPU computing expose the gap quickly.
Linux driver support has at least improved. Early RK3399 systems often relied on old vendor kernels and proprietary Mali components, resulting in an uneven desktop experience and making system upgrades difficult. The open-source Panfrost driver now supports the Mali-T860, so current Linux distributions have a much more practical graphics stack than the RK3399 had during its first few years.
It Was Never Just an SBC Processor
Most people now encounter the RK3399 on boards such as the Rock Pi 4, NanoPi M4, Orange Pi 4, or Pinebook Pro. That makes it easy to think of the chip primarily as an SBC processor, but Rockchip had broader plans. The RK3399 also appeared in Chromebooks, tablets, digital signage players, industrial modules, robotics controllers, media devices, and early ARM laptops.
The RK3399 specification helps explain why. HDMI 2.0a, DisplayPort, eDP, MIPI, PCIe, USB Type-C, Gigabit Ethernet, and dual camera inputs created room for very different hardware designs. The processor could drive an internal eDP panel while providing an external display output, and PCIe could be used for NVMe storage or another high-speed controller. USB 3.0 also made external storage practical rather than merely possible.
This flexibility helped the RK3399 survive outside the enthusiast board market. An industrial terminal, payment system, or information display doesn’t need to win benchmark comparisons every year. Once its hardware, operating system, enclosure, and certifications are complete, replacing the processor may create more work than it saves. Our look at hardware inside Suica readers illustrates the same principle: long-lived interfaces and predictable operation can matter more than using the newest available processor.
4K Playback Is Easier Than 4K Creation
Multimedia was one of the RK3399’s strongest areas. Its hardware video decoder supports H.265, H.264, and VP9 at up to 4K, together with HDR10 and HLG. That was useful for media boxes, digital signage, and ChromeOS devices in 2016, and it remains enough for most conventional 4K playback today.
The encoder is considerably more limited. Hardware H.264 encoding tops out at 1080p, so the RK3399 is a poor foundation for modern 4K recording, high-resolution transcoding, or multi-camera video processing. It is much better at displaying finished content than creating it.
There is also the familiar difference between hardware capability and actual software support. Having a video decoder inside the SoC doesn’t guarantee that a browser, player, or Linux distribution will use it correctly. A well-supported RK3399 board can play high-resolution video while placing little load on the CPU, whereas an outdated system image may fall back to software decoding and perform much worse with the same file.
Linux Support Is Now One of Its Best Features
When the RK3399 was new, buying a board often meant accepting whichever modified kernel the manufacturer supplied. That kernel might provide a working GPU and video acceleration, but it could also be several releases behind upstream Linux. Updates were risky, documentation varied in quality, and support sometimes ended when the manufacturer released its next board.
The situation is better now. Mainline Linux supports the RK3399 platform and many of its important components, including PCIe, thermal monitoring, Ethernet, and the Rockchip ISP1 camera subsystem. Panfrost covers the Mali-T860 GPU, while distributions such as Armbian provide maintained images for several popular RK3399 boards. Years of community testing have also uncovered many of the problems that tend to appear only after hardware reaches real users.
Still, “RK3399 supports Linux” is too broad to be useful on its own. One board may have reliable GPU acceleration, suspend, NVMe, audio, and hardware video decoding, while another may boot the same distribution but require manual work for half of those features. The specific board, kernel, and operating-system image matter more than the general reputation of the processor. This mature software base is a strong reason to maintain an existing RK3399 product, but it is less convincing as a reason to start a new design.
The Missing NPU Is Becoming a Problem
The standard RK3399 doesn’t contain an NPU. Rockchip later introduced the RK3399Pro, which uses a similar CPU and GPU configuration but adds a dedicated neural processing unit. Despite the similar name, it should be treated as a separate platform. Software designed for the RK3399Pro’s NPU won’t gain hardware acceleration on an ordinary RK3399 board.
That distinction didn’t matter much when the original processor was released. In 2026, local inference and machine vision are common requirements even for mid-range embedded systems. A USB or PCIe accelerator can add AI capability to an RK3399 device, but it increases cost, occupies an interface, and introduces another software stack that must be maintained.
For a new AI product, it generally makes more sense to start with a processor that already includes an NPU. The newer RK3576 processor design combines four Cortex-A72 cores, four Cortex-A53 cores, and a 6 TOPS NPU. In some ways, it resembles a modern continuation of the RK3399 idea: retain a mixture of large and small CPU cores, but add the graphics, media, and AI hardware expected from a current embedded processor.
RK3399 vs RK3588
Comparing the RK3399 with the RK3588 makes the age gap obvious. The RK3588 has twice as many performance cores, and those cores use the much newer Cortex-A76 architecture. It also provides a substantially faster GPU, an integrated NPU, newer memory support, and a media engine designed for up to 8K video.
| Feature | RK3399 | RK3588 |
| Performance cores | 2× Cortex-A72 | 4× Cortex-A76 |
| Efficiency cores | 4× Cortex-A53 | 4× Cortex-A55 |
| GPU | Mali-T860 MP4 | Mali-G610 MP4 |
| Manufacturing process | 28 nm | 8 nm |
| NPU | None | 6 TOPS |
| Maximum video decoding | 4K | 8K |
The difference is noticeable in software compilation, desktop multitasking, emulation, AI inference, and almost any workload that can keep several cores busy. The RK3399 isn’t simply a cheaper version of the same experience, and no amount of software optimization can close such a large architectural gap.
But not every project needs the additional hardware. An information display showing a web interface doesn’t care about 8K decoding or a 6 TOPS NPU, and neither does a lightweight server that spends most of its time idle. For workloads that can use the extra performance, our guide to RK3588 architecture and speed explains what the newer processor changes in practice.
Should You Still Buy an RK3399 Board?
For an existing commercial product, continuing with the RK3399 can be reasonable. Replacing a stable design may require a new carrier board, operating-system changes, thermal testing, EMC testing, and another round of application validation. A faster processor doesn’t make those costs disappear, particularly when the current hardware already handles its workload.
Used and discounted RK3399 development boards can also make good Linux systems. The software ecosystem is mature, NVMe is available on many boards, and the Cortex-A72 cores still provide acceptable performance for self-hosted services, media playback, and light desktop use. At full price, however, the argument becomes harder. An RK3566 board may run cooler and include a small NPU, while the RK3576 and RK3588 offer far more performance and room for future software requirements.
The RK3399 isn’t a bad processor. It’s simply no longer the processor we would design around unless an existing software base, a particular board, or a very good price justified the compromise. Remaining useful almost ten years after release is impressive, but longevity and competitiveness aren’t quite the same thing.