Intel HD Graphics 400 Mobile

Benchmark Performance

The Intel HD Graphics 400 Mobile presents an unusual case in the benchmark database: it carries no direct benchmark scores of its own, and its average benchmark score is recorded as zero. Its percentile ranking against all GPUs sits at exactly 50, which places it in the middle of the distribution, though this figure is somewhat misleading given the absence of measured workloads. The data suggests this is a part that was never subjected to the standard benchmark suite, or whose results were not retained in the database.

What can be interpreted from the specifications is the theoretical ceiling. The GPU delivers 115.2 GFLOPS of FP32 compute, which is derived from 96 shading units operating at a 600 MHz boost clock. Pixel throughput is rated at 1.200 GPixel/s, and texture fill rate comes in at 7.200 GTexel/s. These are extremely modest figures by any modern standard, and they align with the part's positioning as an integrated graphics solution for low-power mobile devices. The 50th percentile ranking, in context, likely reflects the fact that many comparable integrated parts from the same era are similarly limited, rather than indicating any competitive strength.

Because the nearestRivals array is empty, there are no direct percentage deltas to report against specific competitors. This absence of comparative data means the analysis must rely on architectural context. The chip is built on Generation 8.0 architecture with a Braswell GT1 die, fabricated on Intel's 14 nm process. The Airmont generation label for the HD Graphics-T series indicates this is a low-end SKU designed for basic visual output, not for gaming or content creation workloads. In the absence of rival scores, the FP32 figure of 115.2 GFLOPS serves as the primary quantitative anchor, and it signals performance that would be challenged by even entry-level discrete graphics solutions from the same period.

Power and Cooling

The thermal design power for the Intel HD Graphics 400 Mobile is remarkably low at 6 W. This figure encompasses the entire graphics subsystem, which is expected given the integrated nature of the part. There is no suggested PSU rating listed in the fact pack, and no power connector requirements are specified. This is consistent with an IGP slot width, meaning the GPU is not a separate card but rather embedded within the processor package or motherboard.

Cooling requirements are minimal by necessity. A 6 W TDP generates very little heat, and in typical implementations, the surrounding system cooling, whether a laptop chassis fan or a low-profile desktop cooler, would be more than sufficient. The data indicates no dedicated cooling solution is required, and the absence of power connectors suggests the GPU draws its power entirely from the motherboard's standard power delivery rails. For system builders, the implication is that this part imposes no additional burden on the power supply unit. Any PSU capable of powering the host system will adequately support this GPU. The low TDP also means that thermal throttling is unlikely to be a significant factor in most usage scenarios, though the low boost clock of 600 MHz suggests the headroom is already quite constrained.

How It Compares

The nearestRivals array is empty for this entry, so there are no direct comparative paragraphs to write against named competitors. The database has not recorded any rival GPUs with scores and deltaPct values for this part. This is unusual but not unprecedented for integrated graphics from the low-power segment, especially for a product that is marked as end-of-life. The absence of rivals means the GPU's position must be inferred from its own specifications and the broad percentile ranking.

What can be said is that the 50th percentile ranking, combined with zero benchmark scores, creates an ambiguous profile. In the absence of rival data, the most honest assessment is that this GPU occupies a niche where quantitative comparison is not possible from the available facts. The architectural details, 96 shading units, 2 ROPs, 12 TMUs, paint a picture of a part that is significantly less capable than even the weakest discrete GPUs of its era. The 14 nm process is a point in its favor for efficiency, but the 320 MHz base clock and 600 MHz boost clock indicate that the designers prioritized power savings over performance. Without rival scores, the analysis must stop at this qualitative boundary.

FAQ

Q: What is the FP32 compute performance of the Intel HD Graphics 400 Mobile?

A: The FP32 performance is rated at 115.2 GFLOPS, based on 96 shading units at a 600 MHz boost clock.

Q: What is the TDP and does it require a dedicated power connector?

A: The TDP is 6 W, and no power connectors are listed. The slot width is IGP, meaning power is drawn from the motherboard.

Q: What is the memory configuration for this GPU?

A: The memory size, type, and bus width are all listed as "System Shared," meaning the GPU uses the host system's RAM. Bandwidth is described as "System Dependent."

Q: What APIs are supported?

A: The GPU supports DirectX 12 (11_1), OpenGL 4.3, and Vulkan 1.0.

Q: Is this GPU still in production?

A: No, the production status is "End-of-life," with a release date of March 31, 2015.

Q: What is the pixel and texture fill rate?

A: The pixel rate is 1.200 GPixel/s, and the texture rate is 7.200 GTexel/s.

Ray Tracing and Feature Set

The fact pack explicitly lists no RT cores and no tensor cores for this GPU. This is expected for a Generation 8.0 architecture from 2015, as hardware ray tracing acceleration was not part of Intel's integrated graphics roadmap at that time. The absence of these cores means any ray tracing workload would be handled by the compute units, which are already severely limited at 115.2 GFLOPS. The data strongly implies that ray tracing is not a practical feature for this part.

The API support, however, is more forward-looking than the hardware suggests. DirectX 12 (11_1) support means the GPU can run titles that use the newer API, though the feature level of 11_1 limits what can be exposed. Vulkan 1.0 support is also present, which provides access to modern low-overhead rendering paths. OpenGL 4.3 rounds out the API set. These APIs do not compensate for the raw compute deficit, but they do mean the driver stack is modern enough to run contemporary software. The display outputs are listed as "Portable Device Dependent," which confirms this is primarily a mobile part where the display connection is determined by the laptop or tablet design. The bus interface is "Ring Bus," which is typical for integrated graphics in this era, connecting the GPU to the rest of the processor package.

Who Should Consider It

Given the 50th percentile ranking and the zero benchmark score, the Intel HD Graphics 400 Mobile is not a part that should be considered for any form of modern gaming or graphics-intensive work. The FP32 figure of 115.2 GFLOPS is the key limiting factor. At 1080p resolution, even esports titles with low graphical requirements would struggle to maintain playable frame rates, and the 1.200 GPixel/s pixel rate constrains fill-rate-heavy effects. The 2 ROPs are a particular bottleneck for high-resolution rendering, as ROP count directly affects the ability to write pixels to the framebuffer.

The realistic use case is basic desktop productivity, video playback, and lightweight 2D applications. The 6 W TDP makes this part suitable for fanless designs and ultra-portable devices where battery life is prioritized over performance. For users who need to run modern 3D games, the data points to a need for a discrete GPU, but no rival data is available to recommend a specific alternative. For users whose workload is limited to web browsing, office suites, and streaming video, the HD Graphics 400 Mobile is adequate, provided the system has sufficient shared memory. The "System Dependent" bandwidth means that dual-channel memory configurations will yield better performance than single-channel, but the fact pack provides no specific numbers to quantify this difference.

Memory Subsystem

The memory subsystem for the Intel HD Graphics 400 Mobile is entirely system-shared. There is no dedicated VRAM; instead, the GPU accesses the host system's RAM. The memory size, type, and bus width are all listed as "System Shared," which means these parameters are not fixed by the GPU but rather determined by the host platform. The bandwidth is described as "System Dependent," indicating that the memory performance will vary based on the system's memory configuration, including whether dual-channel mode is enabled and the speed of the system RAM.

This architecture is common for low-power integrated graphics, as it reduces cost and complexity. However, the lack of dedicated memory has performance implications. Because the GPU shares the memory bus with the CPU, memory-intensive workloads can cause contention. At high resolutions, where the framebuffer footprint is larger, the system-dependent bandwidth can become a limiting factor. The 2 ROPs further constrain high-resolution performance, as they limit the rate at which pixels can be written to the framebuffer. For 1080p gaming, the shared memory architecture would likely result in stuttering and low frame rates, particularly in scenes with high texture detail. The fact pack provides no specific bandwidth numbers, so the analysis must remain qualitative: the memory subsystem is adequate for basic tasks but will not support demanding graphical workloads. The "System Shared" designation appears repeatedly across the memory fields, underscoring that this GPU is entirely dependent on the host system for all memory functions.