Case · MODEL NOTES

LIAN LI O11 VISION COMPACT Black (O11VPX)

Choose the roof mode first: the glass showcase and top-radiator layouts are different builds.

The decision

O11 VISION COMPACT Black makes the visible components part of the room, with a dual-chamber layout and a choice of glass or mesh roof. That choice has a functional consequence. Plan the cooling mode, then route the build around it rather than adding a top AIO to a configuration intended to keep the glass roof.

Consider it when

  • A showcase build where side and bottom airflow have been deliberately planned.
  • A mesh-roof configuration needing top-mounted fans or a radiator.

Look again when

  • Expecting top cooling hardware to work in glass-roof mode.
  • An E-ATX board at 280 mm width or a PSU at 220 mm treated as an unconditional fit.

The checks that can change your choice

Keep the selected mode visible in the plan

Top fans and radiators require mesh mode. Check side and bottom stacks with the GPU and cables too; changing the roof after ordering cooling parts can alter the usable arrangement.

Count the four drive positions correctly

There are two dedicated 2.5-inch positions and two shared 2.5/3.5-inch bays. The shared bays do not double their capacity when you mix drive sizes, and routing still needs room beside the PSU.

Published specifications

Dual-chamber ATX showcase case; mesh or glass top; GPU up to 408 mm; CPU cooler up to 167 mm; top/side/bottom radiator positions; up to four drives.

BrandLIAN LI
Exact modelO11 VISION COMPACT Black (O11VPX)
Manufacturer model numberO11VPX
Form factorMid-tower
Case motherboard supportE-ATX, ATX, micro-ATX, Mini-ITX
Case motherboard width limitStrictly below 280 mm; check the exact board width, not only its format name
Case GPU length limit408 mm; cooling and layout can reduce this
Case CPU cooler height limit167 mm
Case PSU formatsATX
Case PSU length limit220 mm; allow cable and drive-cage space
PSU limit conditionPSU length must be strictly below the stated limit.
Radiator mount: top / 240 mmMesh top mode only.
Radiator mount: top / 280 mmMesh top mode only.
Radiator mount: top / 360 mmMesh top mode only.
Radiator mount: side / 240 mmCheck radiator width; GALAHAD II Trinity Performance is excluded by the manufacturer.
Radiator mount: side / 360 mmCheck radiator width; GALAHAD II Trinity Performance is excluded by the manufacturer.
Radiator mount: bottom / 240 mmCheck GPU clearance and pump position; bottom radiator is not automatically suitable for an AIO.
Radiator mount: bottom / 360 mmCheck GPU clearance and pump position; bottom radiator is not automatically suitable for an AIO.
Drive mount behind-motherboard2 dedicated position(s) for 2.5 inch
Drive mount drive-cage2 shared position(s) for 2.5 inch or 3.5 inch; sizes within this group use the same positions
Fan mount: top / 120 mm3 positions; 0 fan(s) included; Mesh mode only; shared with top radiator.; shares positions with another size or arrangement
Fan mount: top / 140 mm2 positions; 0 fan(s) included; Mesh mode only; alternative to three 120mm fans.; shares positions with another size or arrangement
Fan mount: side / 120 mm3 positions; 0 fan(s) included
Fan mount: bottom / 120 mm3 positions; 0 fan(s) included
Fan mount: rear / 120 mm2 positions; 0 fan(s) included

Top fans/radiators require mesh mode. PSU limit is under 220mm; E-ATX motherboard width must be under 280mm. Two dedicated 2.5-inch positions plus two shared 2.5/3.5-inch bays. Fan and radiator positions overlap; final stack and cable clearances require review.

A different choice worth checking

These alternatives address related choices. Recheck their platform, connections and fit before treating one as a replacement.

Follow the check that matters to your build

Sources and review notes

RigAtlas connects manufacturer specifications to component choices. This page is document-based analysis; it does not claim a hands-on test or a current store offer.

How we use sources · Report a correction

See how it fits your list.

Review this component with your existing selections before making the change.

Check with my build