Skip to content
Oculr
Browser kernel versions

Pin each profile to a real engine

Oculr ships 16 pinned Chromium kernels, from Chrome 132 to the current majors. Pin a profile to an exact version and its user agent and client hints always match the engine running underneath, with kernels managed right inside the app.

16
Pinned Chromium kernels
Chrome 132
Earliest version available
Current majors
Ported as they ship
The kernel range

16 pinned browser kernel versions, one per profile

Every kernel is a vendored, registered Chromium build. Pin a profile to the version it needs, and its user agent and client hints come from that same engine.

From Chrome 132 to the current majors

The full registry of pinned Chromium versions, vendored and ready to pin. Run an older engine for compatibility work or a current one to match the browsers your users have today.

Pinned per profile

Each profile locks to one exact kernel. The UA string, client hint brands and feature flags all derive from that version, so what a profile reports matches the code rendering the page.

Managed in the app

An Update Center lists every kernel with its install state and size on disk, installs and uninstalls with progress tracking, and adds new Chrome majors as they ship.

Mix versions across a fleet

Keep a spread of engine versions across your profiles when your work needs it, each one honest about the version it actually runs.

Why it matters

A reported version is only worth what's behind it

Claiming to be Chrome 146 means nothing if the engine rendering the page is something else. Oculr pins the real kernel, so the version a profile reports is the version it runs.

Pin a profile to one of 16 Chromium kernels and its user agent, the string a browser sends to declare its version, and its client hints all derive from that exact version. The same pinned engine carries the native antidetect engine that powers the rest of Oculr, so what a profile reports stays honest about the code rendering the page.

16 Chromium kernels, from Chrome 132 to current

Every kernel is a vendored, registered Chromium build. Pin a profile to an older engine for compatibility work or to a current one to match the browsers your users run today, and keep a spread of versions across a fleet when you need it.

  • 16 pinned Chromium versions on hand
  • Chrome 132 through the current majors
  • Mix versions across a fleet as your work needs
kernel registry5 of 9 installed
132
168 MB
136
178 MB
139
183 MB
141
191 MB
143
199 MB
144
203 MB
146
207 MB
147
210 MB
148
214 MB
16 versions from Chrome 132 to the current majors

UA and client hints that match the engine underneath

The user agent string, client hint brands and feature flags all derive from the pinned kernel through a registry. There is no daylight between what a profile claims and the code actually rendering the page, because both come from the same version.

  • Profiles pinned to an exact kernel version
  • UA and client hints derive from that version
  • No gap between the reported version and the real engine
ecom-de-04 · pinned engine
Pinned kernelChrome 146
User agent...Chrome/146.0.0.0
sec-ch-ua"Chromium";v="146"
Feature flagsv146 set
What a profile reports matches the engine it runs

Manage kernels in the app, stay current

A picker in the profile editor and a Settings page list every kernel with its install state and size on disk. The Update Center installs and uninstalls with progress tracking, and new Chrome majors are ported as they ship, so you install what you need and stay current.

  • See what is installed, install what you need
  • Install state and on-disk size for every kernel
  • New Chrome majors ported as they ship
update center
Chrome 148214 MBInstalled
Chrome 147210 MB64%
Chrome 134199 MBInstall
Chrome 132183 MBInstall
FAQ

Frequently asked questions

What is a browser kernel version?+

A kernel is the actual browser engine a profile runs on. In Oculr, each profile is pinned to a specific Chromium-based kernel version, and that version drives the user agent string, the client hint brands and the feature flags. Pinning the kernel is what keeps a profile's reported version honest about the engine underneath it.

How many kernel versions does Oculr offer?+

Oculr ships 16 pinned Chromium kernel versions, spanning Chrome 132 through the current majors. Each one is vendored and registered, so you can pin a profile to an older engine for compatibility testing or to a current one to match today's browsers.

Will the user agent match the engine actually running?+

Yes. The UA string and client hint brands derive from the pinned kernel version through a registry, so what a profile reports always matches the real engine running underneath. There is no gap between a claimed version and the code rendering the page.

Can I manage kernels from inside the app?+

Yes. A two-tier picker in the profile editor and a Settings page list every kernel with its install state and size on disk, and an Update Center installs, uninstalls and tracks progress. You install the versions you need and keep the rest off your disk.

Do new Chrome versions get added?+

Yes. New Chrome majors are ported as they ship, so your fleet can stay current with the browsers your users actually run. The most recent majors landed within the same cycle as upstream.

Pin every profile to a real engine

Spin up your first two profiles free, pick the Chromium versions you need, and pin each profile to the engine that fits the job.

No credit card required · Cancel anytime