Brave always returns tier 0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Brave Browse on Intel 2019 Macbook Pro (Ventura 13.2) always reports tier 0.
Chrome on the same machine correctly reports tier 3.
Brave:
{
"wasm": true,
"simd": true,
"webgl": true,
"webgl2": true,
"offscreen": true,
"browser": {
"name": "chrome",
"version": "112.0.0",
"os": "Mac OS",
"type": "browser"
},
"gpu": {
"fps": 14,
"gpu": "amd radeon pro 5300m",
"isMobile": false,
"tier": 0,
"type": "BENCHMARK",
"hwaccel": false
},
"supportedInBrowserList": true
}
Chrome:
{
"wasm": true,
"simd": true,
"webgl": true,
"webgl2": true,
"offscreen": true,
"browser": {
"name": "chrome",
"version": "112.0.0",
"os": "Mac OS",
"type": "browser"
},
"gpu": {
"fps": 130,
"gpu": "amd radeon pro 5300m",
"isMobile": false,
"tier": 3,
"type": "BENCHMARK",
"hwaccel": true
},
"supportedInBrowserList": true
}
Hardware acceleration is enabled in Brave and confirmed to work on multiple sites.

Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported comparison on the Intel 2019 MacBook Pro in Brave and Chrome, using the GPU result shown in the issue. Inspect the browser and hardware-acceleration detection path to determine why Brave reports false acceleration and tier 0; done means Brave reports the expected acceleration state and tier without regressing Chrome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100