GPU models library — graphics card database

Browse real-world GPU renderer strings collected via WebGL on CheckProxy.org. Filter by vendor and platform (PC, Laptop, Workstation, Mobile), export lists, and read our GPU guide below.

1192 entries in library · Last updated Jul 29, 2026, 02:20 AM

GPU models library update 2026

Manage GPU models
# GPU renderer Vendor Platform
351 Mali-G720 MC7 ARM Mali Mobile
352 ANGLE (Samsung Xclipse 540) on Vulkan 1.3.279 PC
353 ANGLE (NVIDIA, NVIDIA GeForce GT 730 (0x00000FC9) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
354 ANGLE (AMD, Radeon Pro Vega 20 Direct3D11 vs_5_0 ps_5_0, D3D11) AMD Workstation
355 ANGLE (Intel, Intel(R) HD Graphics 610 (0x00005902) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
356 Adreno (TM) 540, or similar Qualcomm Mobile
357 ANGLE (NVIDIA, NVIDIA T1000 (0x00001FB0) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
358 ANGLE (AMD, AMD Radeon R7 200 Series (0x00006613) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
359 Adreno (TM) 825 Qualcomm Mobile
360 ANGLE (Apple, Apple M1 Pro, OpenGL 4.1) Apple Laptop
361 Adreno (TM) 430, or similar Qualcomm Mobile
362 ANGLE (Microsoft, Microsoft Basic Render Driver Direct3D11 vs_5_0 ps_5_0, D3D11) PC
363 ANGLE (AMD, AMD Radeon (TM) R7 350 Direct3D11 vs_5_0 ps_5_0, D3D11-26.20.13031.18002) AMD PC
364 ANGLE (NVIDIA, NVIDIA GeForce GTX 660 (0x000011C0) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
365 ANGLE (NVIDIA, NVIDIA GeForce GT 625 (OEM) (0x0000104B) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
366 Adreno (TM) 642L Qualcomm Mobile
367 ANGLE (Intel, Intel(R) HD Graphics 530 Direct3D11 vs_5_0 ps_5_0, D3D11-27.20.100.9316) Intel Laptop
368 ANGLE (Intel, Intel(R) HD Graphics 400 Direct3D11 vs_5_0 ps_5_0), or similar Intel Laptop
369 ANGLE (NVIDIA, NVIDIA GeForce MX330 (0x00001D16) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
370 ANGLE (Intel, Intel(R) UHD Graphics 730 (0x00004682) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
371 ANGLE (Apple, ANGLE Metal Renderer: Apple Paravirtual device, Unspecified Version) Apple Laptop
372 ANGLE (Intel, Intel(R) HD Graphics 4600 (0x00000416) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
373 ANGLE (NVIDIA, NVIDIA GeForce GTX 1650 Ti (0x00001F95) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
374 ANGLE (NVIDIA, NVIDIA GeForce GTX 1650 SUPER (0x00002187) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
375 ANGLE (Intel, Intel(R) Iris(R) Plus Graphics (0x00008A52) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
376 ANGLE (Qualcomm, Adreno (TM) 720, OpenGL ES 3.2) Qualcomm Mobile
377 ANGLE (Intel, Intel(R) HD Graphics 510 (0x00001902) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
378 Android Emulator OpenGL ES Translator (Google SwiftShader) Mobile
379 ANGLE (AMD, AMD Radeon RX 5600 OEM (0x0000731F) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
380 ANGLE (Intel, Intel(R) UHD Graphics 730 (0x00004C8B) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
381 ANGLE (NVIDIA, NVIDIA GeForce GTX 1650 (0x00001F91) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
382 ANGLE (NVIDIA, NVIDIA GeForce RTX 3060 (0x00002544) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
383 ANGLE (ARM, Mali-G77, OpenGL ES 3.2) ARM Mali Mobile
384 ANGLE (Intel, Intel(R) Iris(R) Xe Graphics 0x000046A0A Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
385 ANGLE (AMD, AMD Radeon R7 430 Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
386 Apple A17 Pro GPU Apple Laptop
387 Samsung Xclipse 540 PC
388 PowerVR Rogue GE8322 PowerVR Mobile
389 ANGLE (Intel, Intel(R) HD Graphics 510 Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
390 ANGLE (AMD, AMD Radeon HD 6450 Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
391 ANGLE (Intel, Mesa Intel(R) UHD Graphics (TGL GT1), OpenGL 4.6) Intel Laptop
392 ANGLE (Imagination Technologies, PowerVR Rogue GE8322, OpenGL ES 3.2) PowerVR Mobile
393 ANGLE (NVIDIA Corporation, NVIDIA GeForce GT 750M OpenGL Engine, OpenGL 4.1) NVIDIA PC
394 ANGLE (Apple, ANGLE Metal Renderer: Apple M2 Pro, Unspecified Version) Apple Laptop
395 ANGLE (AMD, AMD Radeon(TM) 660M (0x00001681) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
396 Mali-G72 MP3 ARM Mali Mobile
397 ANGLE (AMD, AMD Radeon(TM) Graphics (0x0000163F) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
398 ANGLE (NVIDIA, NVIDIA GeForce RTX 4060 (0x00002808) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
399 ANGLE (Intel, Intel(R) UHD Graphics Direct3D11 vs_5_0 ps_5_0, D3D11-26.20.100.8141) Intel Laptop
400 ANGLE (AMD, ASUS Radeon RX 580 Series (0x000067DF) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC

What is a GPU and why this library exists

A Graphics Processing Unit (GPU) is a specialized processor that renders images, video, and 3D scenes. Modern GPUs power everything from desktop gaming and creative workstations to thin laptops and smartphones. On the web, browsers expose a subset of GPU identity through WebGL and WebGPU APIs — often as a renderer string such as "ANGLE (NVIDIA GeForce RTX 3060)".

CheckProxy.org maintains a community GPU models library built from anonymous WebGL scans submitted via our My GPU tool. Each entry records the renderer name, vendor, inferred device platform (PC, Laptop, Workstation, or Mobile), and when it was last seen. Use this page to research graphics hardware, compare renderer strings, or verify what your browser reports.

Unlike a retail spec sheet, this database reflects real-world browser fingerprints — useful for developers, QA teams, privacy researchers, and anyone running antidetect or multi-profile workflows who needs to know how a GPU appears online.

A brief history of GPUs

Dedicated graphics chips appeared in the 1980s (IBM Professional Graphics Adapter, early workstation cards). Consumer 3D acceleration took off in the mid-1990s with 3dfx Voodoo, NVIDIA RIVA, and ATI Rage — enabling real-time 3D in PC games.

The 2000s brought programmable shaders (DirectX 9 / OpenGL 2), unified architectures, and mobile GPUs (PowerVR, Adreno, Mali). Apple Silicon and AMD/NVIDIA RTX lines dominate the 2020s, while WebGL (2011) and WebGPU (2020s) let websites query GPU capabilities without installing drivers.

Today, renderer strings in browsers may differ from the physical card label because of driver layers (ANGLE on Windows), virtualization, or privacy hardening. Our library captures those strings as observed — making it a practical reference for web-facing GPU identity.

GPU terms & technical definitions

Key concepts you will see in the table above and in browser developer tools.

GPU renderer (WebGL)
The UNMASKED_RENDERER_WEBGL string returned by the browser — often includes brand, model, and driver layer (e.g. ANGLE, Metal). This is the primary key in our library.
Vendor
The graphics chip manufacturer reported alongside the renderer — typically NVIDIA, AMD, Intel, Apple, Qualcomm, ARM, or Microsoft (for basic renderers).
WebGL
A JavaScript API for 2D/3D graphics inside the browser. WebGL 1.0/2.0 exposes limits such as max texture size and the renderer/vendor pair used for fingerprinting studies.
WebGPU
The successor to WebGL — lower overhead, modern GPU compute. Support varies by browser/OS; many entries in our library predate wide WebGPU adoption.
VRAM (video memory)
Dedicated memory on discrete GPUs (or shared system RAM on integrated/mobile chips). Browsers do not reliably expose VRAM size; infer capacity from model names or vendor documentation instead.
Platform type
Our classification of where the GPU is typically used: PC (desktop), Laptop (portable / integrated / Max-Q), Workstation (Quadro, Radeon Pro, datacenter cards), or Mobile (phone/tablet SoC GPUs).

Frequently asked questions about GPUs

Common questions about GPU renderer strings, browser detection, and the CheckProxy.org graphics library.

It is the text your browser returns from WebGL (UNMASKED_RENDERER_WEBGL) describing the active graphics adapter — for example "Apple M2" or "ANGLE (NVIDIA, NVIDIA GeForce GTX 1660 SUPER Direct3D11 vs_5_0 ps_5_0, D3D11)". Sites can read it with JavaScript; our library stores anonymized copies from user scans.

Browsers often report through abstraction layers: ANGLE translates OpenGL ES to Direct3D on Windows; dual-GPU laptops may use the integrated chip for the browser while games use discrete; remote desktop and VMs show virtual adapters. The renderer string reflects what the browser stack sees, not always the physical card name.

WebGL maps to OpenGL ES and has been supported broadly since the early 2010s. WebGPU is a newer, lower-level API with better compute support. Fingerprinting and capability checks may use either; our My GPU page reports both when available.

When you run a scan on My GPU, the renderer, vendor, and related WebGL limits may be sent once per unique string (rate-limited, no login). Duplicates increment a hit counter and update last-seen timestamps. You can browse results here without scanning.

Yes. Any script on a page can create a WebGL context and read the renderer/vendor unless the browser or an extension blocks or spoofs it. This is one signal in browser fingerprinting — alongside canvas, fonts, and IP. Use our antidetect and fingerprint tools to audit your profile.

Integrated GPUs (Intel UHD/Iris, AMD APU, Apple unified memory) share system RAM and often appear in laptops. Discrete GPUs (GeForce, Radeon RX) have dedicated VRAM and usually show full model names. Workstation cards (Quadro, Radeon Pro) may report professional branding. Mobile SoCs use Adreno, Mali, or Apple GPU strings.

GPU vendor popularity ranking

Vendors sorted by the number of distinct GPU renderer strings recorded in our library. Click a vendor to browse all models from that manufacturer.

Don't see your card? GPU & WebGL