Loading ApexMark…

Free Online CPU, GPU & RAM Benchmark

Run a CPU benchmark, GPU benchmark (WebGPU) and RAM speed test in one browser run. See the real work as it happens, with no installation.

Why ApexMark

One platform.
A complete view
of performance.

ApexMark gives you one clear performance picture across computers, phones and operating systems. Run the complete sequence or focus on one measurement, always with the real work visible.

  • One complete profileCPU, graphics, memory, storage and internet in a single place.
  • Visible benchmark workEvery test shows the workload being measured and checks the output it produces.
  • Context for comparisonDevice, operating system, browser and protocol details travel with each result.
How ApexMark keeps comparisons fair

ApexMark is experimental. Its methodology and combined index evolve openly as browser capabilities improve.

Benchmark essentials

Understand the test.
Interpret the result.

How ApexMark measures browser performance and helps you make informed comparisons.

Which devices and browsers can't run the full benchmark?

The graphics test needs WebGPU, the browser feature that lets a page use your graphics processor directly. When it's missing, ApexMark tells you so, still runs the processor, memory, storage and internet tests, and holds back the overall score, which needs graphics. A missing test is never recorded as a zero.

iPhone and iPad: iOS or iPadOS 26 or later. On iOS 18 or earlier the graphics test can't run for now, and installing another browser won't help, because every browser on iPhone uses Safari's engine. Mac: Safari 26 or later on macOS Sonoma or newer; a current Chrome or Edge also works. Android: a current Chrome on Android 12 or later. Windows: a current Chrome, Edge or Firefox, with hardware acceleration on and an up-to-date graphics driver. Older graphics chips and blocked drivers can still be refused, whatever the browser.

Samsung Galaxy phones with Exynos chips (Xclipse graphics) are the best-known case: Chrome has often refused to give WebGPU access to these GPUs. Update Chrome and Android first. If it still fails, Chrome has an experimental switch, “Unsafe WebGPU Support”, at chrome://flags/#enable-unsafe-webgpu. Browsers don't allow links to chrome:// pages, so paste that address into Chrome yourself. It's at your own risk and may not help; set it back to “Default” afterwards. When ApexMark detects this case, the exact steps, with a copy button, are one tap away on the device card and the result screen.

Browser-private file storage is also needed for the storage test. Safari and Firefox show that measurement but don't rank it. The combined score never depends on storage or internet.

How do I get the most accurate score?

Start from a freshly restarted browser: quit it completely, because closing the window isn't always quitting. Close other demanding apps, unused tabs and extensions, plug a laptop in, select its performance power mode and keep the tab visible until the run finishes. Then run the full sequence two or three times, a minute or two apart, and keep the best clean run. Heat, power settings and background load are the biggest sources of noise, not the benchmark itself, and the Hall of Fame keeps your best score anyway. The fastest browser isn't fixed, so it's worth trying more than one: on Windows, start with Edge, then repeat the run in Chrome — driver builds and scheduling differ enough that the winner varies by machine. On macOS, try Chrome and Safari once each and keep the better local result. On Android start with Chrome; on iPhone and iPad start with Safari. If your score looks low next to the same hardware in the Hall of Fame, repeat it in a second browser before drawing conclusions. Once you've found your fastest setup, keep comparisons within that same browser and version — mixing browsers between runs is the easiest way to invalidate a comparison.

How does ApexMark keep comparisons fair across such different devices?

A browser benchmark can't just trust the clock — JavaScript engines, WebGPU, drivers and power management all sit between the test and the hardware. So every workload is versioned and checked: the CPU and memory tests verify each finished piece of work against a published result, and the GPU test climbs a checked resolution ladder rather than trusting one frame. Every score is measured against the same frozen ApexMark 1.0 baseline (1,000 points per category), and a result from a changed protocol gets its own scoreboard rather than being mixed with older ones. Read the full methodology for how each test is built.

Why is my browser benchmark score lower than Geekbench?

The numbers use different scoring scales, so a lower figure alone does not mean your device is slower. ApexMark’s scored categories use the frozen ApexMark 1.0 baseline of 1,000 points.

ApexMark’s CPU test runs in JavaScript workers. Its result reflects the browser engine, scheduling, operating system and power settings as well as the processor. The multi-core phase uses browser-available workers, subject to resource limits and safety checks.

To track changes on your device, repeat ApexMark runs under similar conditions using the same protocol, browser and version, and compare the results and their variation. Read how the CPU benchmark compares with a native tool.

How can the same test run on an entry-level phone and an ultra-high-end GPU?

The GPU test doesn't render one fixed scene — it climbs a resolution ladder from 360p up through 1440p, 4K and 8K, checking and scoring each rung, and stops wherever a device can no longer sustain it. An entry phone isn't forced to choke on a 4K scene, and a flagship GPU isn't capped by a scene too light to challenge it. A separate, verified WebGPU compute pass tests a second, non-visual kind of work. Both parts must complete correctly for a comparable graphics score. The CPU test runs on one thread, then on multiple browser-available worker threads, within resource limits and safety checks. This helps compare supported devices across a broad range without treating an unavailable test as a zero score.

Which CPU, GPU and device benchmarks does ApexMark run?

ApexMark ray-traces an image on your processor (single-core and multi-core), climbs a WebGPU scene through a 360p-to-8K resolution ladder plus a separate compute pass, measures memory bandwidth and latency, and reads and writes a file through your browser's storage. A separate internet test measures download, upload, latency and jitter. You can run the full sequence or any single test.

Do the visuals show actual benchmark work?

Yes. The CPU image appears row by row as your processor finishes it. The GPU view is a scaled copy of the frames being measured. The memory map shows real addresses sampled from the random-access walk, the storage view follows the file blocks being written and read, and the internet chart plots bytes as they arrive.

How is the combined device score calculated?

The frozen ApexMark 1.0 baseline is 1,000 points in every category, and scores scale with measured speed. The overall ApexMark score combines CPU and GPU at 7 parts each and memory at 3 parts, using a geometric mean. Browser storage and internet remain separate measurements and do not affect the device score.

What hardware details can ApexMark detect?

ApexMark reports what the browser exposes. A logical processor count can differ from the number of physical cores. GPU identification may be limited, and browsers do not reliably reveal installed GPU memory or total RAM. Unavailable hardware details stay unknown.

Do I need an account, and where are my results saved?

No account is needed. Runs and results stay in this browser and can be exported. You can also publish a score to the Hall of Fame as a guest: choose a nickname, confirm your hardware, and nothing goes public until you confirm. This browser keeps access to that guest entry, so keep its data if you want to edit it later. Publishing needs a complete score, which includes graphics. Signing in with Google is optional: it adds a private history that follows you across your devices, and carries over what you published as a guest unless that Google account already holds ApexMark data. The internet test exchanges measurement data with a Cloudflare server.

What is Live test, and how is it different from the benchmark?

Live test runs visible CPU rendering, a WebGPU scene, or both continuously, with real FPS after preparation. Adjust the load and follow its history; no live score is saved or submitted. The benchmark uses a fixed, verified protocol for scored measurements. The GPU and combined modes require WebGPU support in your browser and device.

CPU live rendering · GPU live rendering · CPU and GPU together