Skip to content

docs(bot-detection): add GPU Acceleration to Kernel Features That Help #346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guergabo merged 2 commits into from
Apr 27, 2026
+3 −0
Merged

docs(bot-detection): add GPU Acceleration to Kernel Features That Help #346

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
72c1e3f
docs(auth): mention GPU acceleration in Managed Auth feature list
ulziibay-kernel Apr 27, 2026
9882f89
docs(bot-detection): move GPU acceleration to bot-detection overview
ulziibay-kernel Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions browsers/bot-detection/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,9 @@ Kernel automatically applies Patchright to remove automation fingerprints, inclu
Controls the browser without using the Chrome DevTools Protocol (CDP), which can reduce bot detection signals.
Emulates native keyboard and mouse input directly at the OS level and includes human-like [bezier curves](/browsers/computer-controls#move-the-mouse) by default.

### [GPU Acceleration](/browsers/gpu-acceleration)
Many detection systems fingerprint canvas and WebGL rendering output and cross-check it against the claimed GPU. Software-rendered browsers produce pixel hashes that don't match any real consumer GPU, which is a strong bot signal on sites with rendering-based fingerprinting. GPU-enabled Kernel browsers render through real hardware, producing output consistent with a normal user's device.

## Getting Started

Before you start automating your workflow, we recommend that you manually test your website to understand how it behaves with Kernel's browsers. Here's how to do that:
Expand Down
Loading