NVIDIA RTX Spark Review: Best GPU in Any Windows Laptop, With a Bandwidth Catch
N1X GPU leads all Windows rivals in benchmarks; Apple M4 Max retains edge in AI token throughput

NVIDIA's RTX Spark laptops went on sale Friday, and the first independent reviews of production hardware confirm what the chip's architecture suggested when Jensen Huang previewed it at Computex in May: the N1X superchip delivers the most powerful mobile GPU ever shipped inside a Windows laptop, while introducing a unified-memory platform that can run 120-billion-parameter language models locally — a capability that previously required a desktop workstation or cloud compute. Launch-day systems from ASUS, Dell, HP, Lenovo, Microsoft, and MSI start at $2,599 and top out above $4,800 for 128GB configurations. What the reviews also confirm is that the headline 600 GB/s bandwidth figure in NVIDIA's marketing describes the chip's internal die-to-die connection, not the memory bandwidth that governs AI inference speed. That figure is 300 GB/s — roughly half of what Apple ships inside its M4 Max. Understanding the difference between those two numbers explains most of what matters about RTX Spark's position in the AI computing landscape.
A Blackwell GPU Die Inside a Laptop: How the N1X Package Works
The N1X is not a shrunk-down desktop chip or a redesigned laptop processor with an AI accelerator bolted on. It is a two-chiplet, 2.5D package that places two full semiconductor dies side by side in a single physical package, connected by NVIDIA's NVLink-C2C interconnect at 600 GB/s. One die is a MediaTek-designed ARM CPU; the other is a Blackwell RTX GPU die — the same Blackwell architecture shipping in NVIDIA's data-center accelerators, adapted for the power envelope of a consumer laptop.
The CPU die contains 20 ARM cores in two configurations: 10 Cortex-X925 high-performance cores and 10 Cortex-A725 efficiency cores. Both are from ARM's 2024-generation designs, fabricated at TSMC 3nm. The GPU die carries 6,144 CUDA cores in the flagship N1X-H configuration (5,120 in the smaller N1X-S), fifth-generation Tensor Cores with support for NVIDIA's FP4 and NVFP4 precision formats, and fourth-generation RT Cores for hardware ray tracing. Both dies are fabricated at TSMC 3nm.
The two chiplets share a single pool of LPDDR5X-9400 memory, connected via a 256-bit interface. Maximum capacity is 128 GB in the highest configuration, with up to 96 GB accessible to the GPU. The memory bandwidth of that pool — the rate at which either die can read data from DRAM — is approximately 300 GB/s, as confirmed by NVIDIA's product announcement.
This is where the marketing language deserves scrutiny. NVIDIA prominently advertises 600 GB/s bandwidth in product materials, and that figure is accurate for what it describes: the NVLink-C2C connection between the CPU die and the GPU die within the package. NVLink-C2C allows the two processors to exchange data with each other at that speed. But NVLink-C2C does not set the speed at which the GPU reads model weights from DRAM during AI inference. That speed is determined by the LPDDR5X memory controller, which runs at 300 GB/s. For every AI workload that cycles large blocks of model weights from memory — which is most of them — 300 GB/s is the operative number.
The practical precedent is the DGX Spark GB10, the desktop Grace Blackwell system NVIDIA announced at GTC in March 2025 at $3,999. The N1X is essentially a laptop adaptation of that architecture: the GPU die is the same Blackwell family, the CPU design is related, but the N1X removes the high-speed networking interface that made the DGX Spark interoperable with data-center infrastructure. The laptop chip caps sustained power draw at 80 watts, though review units running the ASUS ProArt P16 recorded peak spikes near 138 watts during GPU-intensive workloads.
The N1X-S, the smaller configuration shipping in entry-level systems, carries 18 ARM cores (nine Cortex-X925 and nine Cortex-A725) and 5,120 CUDA cores. It supports up to 96 GB of unified memory. The LPDDR5X bandwidth and NVLink-C2C speed are unchanged between the two configurations; the difference is total CUDA core count, maximum memory capacity, and the number of CPU performance cores available for parallelizable workloads.
A 55-TOPS neural processing unit also occupies the package. That unit handles Microsoft Copilot+ features — recall, live captions, real-time translation. It is not available to third-party software at launch.
GPU Benchmark Results: The Windows Leadership Position Is Real
The 3DMark results from multiple independent review outlets are consistent and unambiguous: the N1X posts the highest mobile GPU scores in any Windows laptop tested to date.
In 3DMark Time Spy Extreme, a DirectX 12 workload that stresses GPU compute and bandwidth, the N1X scores approximately 6,060. The next-strongest competitor, AMD's Ryzen AI Max+ 395 Strix Halo shipped in thin-client desktop configurations, scores roughly 4,689 — a 29 percent gap. Intel's Panther Lake integrated graphics score approximately 3,226.
Ray tracing results extend the gap further. In 3DMark Solar Bay, which tests hardware-accelerated ray tracing, the N1X scores approximately 10,594 versus AMD's 6,047 and Intel's 4,015. The Blackwell fourth-generation RT Cores appear to be particularly effective here, consistent with the performance characteristics of the same architecture in discrete desktop GPUs.
For gaming, Cyberpunk 2077 at 1080p Ultra settings ran at approximately 70 frames per second in early review testing — playable performance that no other Windows laptop integrated GPU has achieved at those settings. Battery life on the Microsoft Surface Laptop Ultra reached 14 hours and 35 minutes in a video-playback test, a figure that holds up even with the chip's peak-power behavior, because the efficiency cores and memory subsystem consume significantly less power during video decode than during 3D rendering or AI inference.
CPU performance tells a more complicated story. In Geekbench 7 multi-core tests, production N1X units from different reviewers scored between 23,571 (Windows Central) and 26,310 (Tom's Guide) — a variance that suggests thermal management or test conditions differ across review configurations. Early PassMark results placed Multi-Thread scores in the range of approximately 42,000, with Single-Thread scores near 4,450.
The single-core figure is where competitive comparison becomes unfavorable. Apple's M5 Pro, shipping in MacBook Pro configurations starting around $2,000, posts single-core Geekbench 7 scores approximately 15–20 percent higher than the N1X. The reason traces directly to ARM core generations: NVIDIA and MediaTek used Cortex-X925 and Cortex-A725, ARM's 2024-generation designs, while MediaTek's own Dimensity 9600 series for smartphones already incorporates the newer ARM Cortex-X4 and Cortex-X2 successor designs. The consumer laptop chip launched with the same-generation cores that Apple surpassed in the M4 series.
AI Inference Realities: CUDA Ecosystem vs. Memory Bandwidth
The most consequential dimension of RTX Spark for AI engineers is not GPU rendering performance but local LLM inference capability, and that capability is shaped by three interacting factors: memory capacity, memory bandwidth, and software ecosystem.
Memory capacity determines which models can run at all. At FP4 precision — the NVFP4 format supported by Blackwell's fifth-generation Tensor Cores — a 70-billion-parameter model requires approximately 35 to 41 gigabytes of storage, depending on quantization implementation. A 64 GB N1X configuration accommodates that model with room left for the KV cache that grows with context length. A 128 GB configuration allows 120-billion-parameter models, which NVIDIA has demonstrated running with a one-million-token context window. No other Windows laptop ships with more than 64 GB of unified memory; the RTX Spark 128 GB configuration is unique on the Windows platform.
Memory bandwidth determines how fast those models generate tokens. Transformer inference is predominantly a memory-bandwidth-bound workload: the GPU continuously loads model weight matrices from DRAM, performs matrix multiplications, and returns results. At 300 GB/s, a 70B FP4 model generates tokens at a rate that reviewers have described as adequate for interactive use. Apple's M4 Max, however, operates at 546 GB/s — more than 80 percent more memory bandwidth than the N1X. For any model that fits within the memory of both platforms, Apple's hardware generates tokens proportionally faster.
The software ecosystem inverts this advantage for a specific but large population of AI developers. CUDA — NVIDIA's parallel computing platform — is the foundation of nearly every major machine learning framework. PyTorch's CUDA backend, TensorRT-LLM, TensorRT, and the CUDA-optimized llama.cpp fork all run on the N1X. Apple's macOS does not support CUDA. AMD's ROCm platform is CUDA's nearest Windows equivalent, but ROCm compatibility with production ML libraries remains incomplete; major frameworks support it officially but with known gaps in specific operator coverage and tool support. Qualcomm's Snapdragon X Elite has no equivalent GPU compute stack for LLM inference at all. Developers who have built pipelines on TensorRT-LLM, fine-tuning workflows that use CUDA-accelerated libraries, or inference servers that depend on NVIDIA-specific kernel optimizations have no equivalent path on an Apple, AMD, or Qualcomm laptop regardless of bandwidth or efficiency differences. For that developer population, the RTX Spark is the first laptop that runs their complete stack locally without cloud infrastructure.
The NPU deserves specific attention because its absence from third-party workflows is architecturally significant and not well-explained in NVIDIA's product messaging. The 55-TOPS NPU on the N1X package is reserved at the firmware and driver level for Microsoft Copilot+ features. Third-party applications and AI frameworks cannot address the NPU at launch. This is not a technical limitation of the hardware itself — it is a platform governance decision between NVIDIA and Microsoft. The consequence is that all third-party local inference runs on the GPU, which draws more power and generates more heat than dedicated neural processing hardware would. NVIDIA's OpenShell agent runtime, announced alongside RTX Spark as a framework for governing local AI agents, does not provide NPU access to external developers.
Windows on Arm Compatibility: Progress With Remaining Gaps
RTX Spark laptops run Windows on Arm, which means applications that require x86 instruction sets run through Microsoft's Prism emulation layer. Prism supports 32-bit and 64-bit x86 applications including those using AVX and AVX2 instruction extensions — a prerequisite for many productivity and scientific computing tools. In practice, most business applications, creative software, and AI developer tools run without modification. Python, Node.js, and the major machine learning frameworks all have native ARM64 builds or work correctly through emulation.
Gaming compatibility is the clearest remaining gap. Kernel-level anti-cheat systems — software that operates at the Windows kernel level to detect cheating — cannot be emulated, and require native ARM64 builds from game publishers. Call of Duty, one of the most-played games in the world, requires an ARM64 build of its Ricochet anti-cheat system that is not yet available; NVIDIA has said it expects support to arrive in 2027. Other major multiplayer titles are in similar situations. Buyers who prioritize gaming access to the full Windows software catalog should verify individual title compatibility before purchasing.
DLSS 5 received an updated model on the same day as the RTX Spark launch. The update reduces the neural network's parameter count by approximately 24 percent, cuts 4K VRAM consumption by roughly 20 percent, and cuts GPU overhead for DLSS neural rendering by approximately half — making it about twice as fast as the previous model at DLSS processing. Multi Frame Generation, which can synthesize up to six display frames from a single rendered frame, benefits from the smaller footprint. These improvements matter practically on RTX Spark because the GPU's 300 GB/s memory bandwidth is a binding constraint during gaming; reducing DLSS's memory footprint frees bandwidth for game rendering. The first title shipping with the updated DLSS 5 model is NBA 2K27.
Where RTX Spark Fits and What Remains Uncertain
RTX Spark occupies a legitimate niche that did not exist before today. Developers who run CUDA workloads, organizations that process sensitive data locally rather than through cloud APIs, and AI practitioners who need to inference 70B or larger models without renting GPU compute all now have a laptop option that did not exist before. The GPU benchmark position on Windows is clear and confirmed across multiple independent reviews.
The competitive comparison with Apple is more nuanced. Apple M4 Max and M5 Pro laptops offer higher single-core CPU performance, significantly higher memory bandwidth, and a tightly integrated software stack optimized for the hardware. For local LLM inference on models smaller than 64GB — the bulk of current open-weight models — Apple's platforms generate tokens faster. For CUDA-dependent workflows, models larger than 96GB, and gaming on Windows, RTX Spark wins. Neither platform is universally superior.
What independent benchmarks have not yet provided is a full LLM throughput comparison across model sizes and quantization levels, tested under equivalent conditions. The production hardware has been available for hours, not weeks. The developer and research community will need time to run systematic evaluations using production N1X units — particularly testing FP4 inference throughput, KV cache behavior at long context lengths, and thermal throttling effects during sustained inference workloads. Those results will determine whether the 300 GB/s bandwidth ceiling matters less than NVIDIA's CUDA-optimized inference stack makes it appear, or whether the token-per-second gap against Apple's higher-bandwidth hardware is wider in practice than the raw figures suggest.
The NPU access question also remains open. NVIDIA and Microsoft have not provided a timeline for opening the 55-TOPS NPU to third-party developers. If that access never arrives, RTX Spark's most power-efficient compute resource stays permanently reserved for Copilot+ features — a position that would make the chip less competitive against future ARM platforms that treat the NPU as a general-purpose resource from day one. How that policy evolves will shape whether RTX Spark's architecture becomes a long-term platform or a transitional design whose successors learn from its access restrictions.