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.

1120 entries in library · Last updated Jul 22, 2026, 11:16 PM

GPU models library update 2026

Manage GPU models
# GPU renderer Vendor Platform
801 ANGLE (AMD, AMD Radeon R6 Graphics Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
802 ANGLE (Intel, Mesa Intel(R) UHD Graphics (CML GT2), OpenGL 4.6) Intel Laptop
803 ANGLE (Qualcomm, Adreno (TM) 750, OpenGL ES 3.2 [email protected] (Git@1z2a3b4c5d6e7)) Qualcomm Mobile
804 Apple GPU (A17 Pro GPU 6-core) - iPhone 15 Pro Apple Mobile
805 ANGLE (Qualcomm, Adreno (TM) 740, OpenGL ES 3.2 [email protected] (Git@3k4l5m6n7o8p9)) Qualcomm Mobile
806 ANGLE (AMD, AMD Radeon 780M (radeonsi phoenix LLVM 20.1.2), OpenGL ES 3.2) AMD PC
807 ANGLE (NVIDIA, NVIDIA GeForce MX350 (0x00001C94) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
808 ANGLE (AMD, Radeon RX 590 Series (0x000067DF) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
809 ANGLE (AMD, Radeon (TM) RX 480 Series (0x000067DF) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
810 ANGLE (Intel, Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1.1) Direct3D9Ex vs_3_0 ps_3_0, igdumd64.dll) Intel Laptop
811 ANGLE (NVIDIA, NVIDIA GeForce GT 630 Direct3D11 vs_5_0 ps_5_0, D3D11-23.21.13.9135) NVIDIA PC
812 Generic Renderer PC
813 ANGLE (NVIDIA, NVIDIA GeForce RTX 3050 OEM (0x00002508) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
814 ANGLE (Intel, Intel(R) HD Graphics 3000 (0x00000126) Direct3D11 vs_4_1 ps_4_1, D3D11-23.21.13.8934) Intel Laptop
815 ANGLE (AMD, Radeon(TM) RX 460 Graphics (0x000067EF) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
816 Android Emulator OpenGL ES Translator (NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2) NVIDIA Mobile
817 ANGLE (NVIDIA, NVIDIA GeForce RTX 5070 Laptop GPU (0x00002D58) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA Laptop
818 ANGLE (Samsung Xclipse 530) on Vulkan 1.3.231 PC
819 ANGLE (Apple, Apple M1 Pro, OpenGL 4.1) Apple Laptop
820 NVIDIA GeForce GTX 980, or similar NVIDIA PC
821 ANGLE (Intel, Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0, D3D11-10.18.10.4242) Intel Laptop
822 ANGLE (NVIDIA, NVIDIA NVS 510 (0x00000FFD) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
823 ANGLE (ARM, Mali-T880, OpenGL ES 3.2) ARM Mali Mobile
824 ANGLE (Intel, Mesa Intel(R) Graphics (LNL), OpenGL ES 3.2) Intel Laptop
825 Apple A15 Bionic Pro GPU Apple Laptop
826 ANGLE (AMD, AMD Radeon R9 M370X OpenGL Engine, OpenGL 4.1), or similar AMD PC
827 Apple A17 Bionic GPU Apple Laptop
828 ANGLE (NVIDIA, NVIDIA GeForce GT 1030 Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA PC
829 ANGLE (NVIDIA, NVIDIA Quadro FX 570 (0x0000040E) Direct3D11 vs_4_0 ps_4_0, D3D11) NVIDIA Workstation
830 ANGLE (AMD, AMD Radeon R7 350 Series (0x0000683F) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
831 ANGLE (AMD, AMD Radeon R9 200 Series (0x00006810) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
832 ANGLE (Samsung Electronics Co. Ltd., ANGLE (Samsung Xclipse 920) on Vulkan 1.3.231, OpenGL ES 3.2) PC
833 ANGLE (Intel(R) UHD Graphics 620 Direct3D11 vs_5_0 ps_5_0) Intel Laptop
834 ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (LLVM 10.0.0) (0x0000C0DE)), SwiftShader driver) PC
835 ANGLE (AMD, AMD Radeon (TM) R9 350 (0x0000682B) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
836 ANGLE (AMD, AMD Radeon HD 5800 Series (0x00001636) Direct3D11 vs_5_0 ps_5_0, D3D11-8.17.10.1433) AMD PC
837 ANGLE (AMD, AMD Radeon HD 6770 (0x000068A8) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
838 ANGLE (Intel, Intel(R) Iris(R) Plus Graphics 655 Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
839 ANGLE (AMD, AMD Radeon(TM) 890M Graphics (0x0000150E) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
840 Google SwiftShader PC
841 Mali-G610 MC6 ARM Mali Mobile
842 ANGLE (Apple, ANGLE Metal Renderer: Apple M3 Max, Unspecified Version) Apple Laptop
843 ANGLE (AMD, AMD Radeon Pro WX 3200 Series (0x00006981) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD Workstation
844 Adreno (TM) 829 Qualcomm Mobile
845 ANGLE (NVIDIA, NVIDIA Quadro P2000 (0x00001C30) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA Workstation
846 ANGLE (NVIDIA Corporation, NVIDIA GeForce GT 640 OpenGL Engine, OpenGL 4.1) NVIDIA PC
847 ANGLE (Intel, Intel(R) UHD Graphics 610 (0x00003EA1) Direct3D11 vs_5_0 ps_5_0, D3D11) Intel Laptop
848 ANGLE (Intel, Intel(R) HD Graphics 4000 (0x00000162) Direct3D9Ex vs_3_0 ps_3_0, igdumdim64.dll-10.18.10.4885) Intel Laptop
849 ANGLE (AMD, AMD Radeon RX 7900 XT (0x744D) Direct3D11 vs_5_0 ps_5_0, D3D11) AMD PC
850 ANGLE (NVIDIA, NVIDIA Graphics Device (0x00002808) Direct3D11 vs_5_0 ps_5_0, D3D11) NVIDIA 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