PowerVR GPU models

All GPU renderer strings reported for PowerVR in the CheckProxy.org library — filter, export, and open detail pages.

3 entries in library · By vendor

PowerVR models — library update 2026

Manage GPU models
# GPU renderer Vendor Platform
1 ANGLE (Imagination Technologies, PowerVR Rogue GE8320, OpenGL ES 3.2) PowerVR Mobile
2 PowerVR Rogue GE8320 PowerVR Mobile
3 ANGLE (Imagination Technologies, PowerVR B-Series BXM-8-256, OpenGL ES 3.2) PowerVR Mobile

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.

Back to GPU library

Don't see your card? GPU & WebGL