Skip to content
← Back to Home

System requirements

Last checked against a build: September 2026

Two things matter before you download: what the machine has to be, and what one open profile costs. Every figure below says where it came from — measured here on a named build and machine, taken from Chromium’s own published requirements, or an estimate we mark as one. Nothing on this page is a number we would have liked.

What we measured

One machine, one build, one date — and all three stand under every line.

The application on diskMeasured
Installed, Liminal takes 359 MB. That is the app alone, before a single profile exists.Measured 2026-09-26 · build 152.0.7977.41 · MacBook Pro (Mac15,6) · Apple M3 Pro · 11 × CPU · 18 GB · macOS 26.5.2
A profile’s own folderMeasured
The four profiles on that machine took 3–10 MB each: the low end is one that was barely used, the high end one that did real work. Whatever a profile browses is cached on top of that and grows until you clear it.Measured 2026-09-26 · build 152.0.7977.41 · MacBook Pro (Mac15,6) · Apple M3 Pro · 11 × CPU · 18 GB · macOS 26.5.2
The macOS the build itself demandsMeasured
The shipped application declares macOS 13 as its minimum and will not start below it. That is read out of the build, not chosen for this page.Measured 2026-09-26 · build 152.0.7977.41 · MacBook Pro (Mac15,6) · Apple M3 Pro · 11 × CPU · 18 GB · macOS 26.5.2

What the operating system has to be

Liminal is built on Chromium, so its floor is Chrome’s floor.

macOS, on Apple SiliconChromium requirement
macOS 13 Ventura or newer. The released macOS build is Apple Silicon only; there is no Intel build to download today.
Windows, on ARM64Chromium requirement
The released Windows build is ARM64, and Chrome’s requirement for a machine with an ARM processor is Windows 11 or newer.
Memory, disk and coresChromium requirement
Google publishes no figure for RAM, free disk space or processor cores for Chrome on either platform. Neither do we: what we have is measured above and estimated below.Chrome system requirements · 2026-09-26

What we can only estimate

Marked as estimates because that is what they are.

Memory for one open profileEstimate, not measured
Expect hundreds of megabytes for a profile with a few tabs open — the same order as a Chrome window with the same tabs, because a profile is a Chromium browser process with a renderer per tab. This follows from what Chromium is; nobody has measured it on Liminal.
How long a profile takes to openEstimate, not measured
Seconds on an SSD rather than tens of seconds: the app is already running and the profile starts inside the window it already has. We have not timed it, so we will not print a number.
How many profiles at onceEstimate, not measured
This follows from your memory and from what each profile has open, so no single figure is honest. Ten light profiles and ten heavy ones are not the same machine.

What is not measured at all

Said plainly, so a missing measurement does not read as a good one.

Windows ARM64Not measured
Nothing on this page was measured on Windows. Every measured line above is the macOS build on one Mac, and the Windows requirement is Chromium’s, not ours.
Memory and start time on our buildNot measured
Both are estimates today. When they are measured, the numbers replace the estimates on this page and carry their own date, build and machine, exactly like the lines above.
Your machine, which is the real testNot measured
The free plan has no profile cap and no clock on it, so the cheapest measurement is your own: open the profiles you actually work with and watch Activity Monitor or Task Manager while they run.

What else you can check without taking our word for it is on the trust, payment and support page. A figure here that does not match what your machine shows: [email protected].