Twinmotion System Requirements 2026: CPU, GPU, RAM & Mac Support

Epic publishes two tiers, not three. There is no middle "recommended" configuration the way some vendors publish it — just a floor for small-to-medium projects and a ceiling for everything past it. Revit, by contrast, publishes three named tiers for the same kind of decision. Neither structure is more correct; it just means a straight side-by-side table between the two tools has to collapse Revit's middle tier or split Twinmotion's in two to line up, and this page keeps Epic's own two-tier shape rather than forcing a third one that Epic never published.

Minimum requirements

Rated for "small to average sized projects that contain less than 1 GB of geometry and data". At this tier you can create local and cloud presentations, export video at 2K, and export stills up to 4K. You explicitly cannot use VR mode, export video at 4K or higher, export 360° video, or use the Path Tracer — Epic states all four as out of scope for the minimum configuration, not as things that merely run slowly.

High-end requirements

Rated for projects over 1 GB of geometry — "large buildings, cities, or large landscapes" in Epic's own phrasing. This tier is what unlocks VR mode, video exports up to 64K, still exports up to 64K, and both the Path Tracer and Lumen rendering modes. Disk space does not change between tiers; only RAM, CPU, and GPU do.

The jump between the two tiers is steep on paper — RAM quadruples, and the GPU has to clear double the VRAM and twice the PassMark score — but the trigger for needing it is a single number: whether the project passes roughly 1 GB of geometry and data. A site model that stays under that line has no reason to buy the high-end configuration just because the project looks large on screen.

There is a real macOS build of Twinmotion, and it has been a native Apple Silicon build — not an emulated Intel one — since Twinmotion 2025.1, which Epic's release notes describe as shipping "as a universal application, meaning it natively supports both Intel and Apple Silicon processors like the M1, M1 Pro, M1 Max, M2, and newer chips." Before that, the Twinmotion 2022.2 specification stated plainly that M1 chips were "not currently fully supported or leveraged for Twinmotion."

The floor moved a long way in the time since. Twinmotion 2022.2 asked for macOS 10.14.6 Mojave, released in 2018. Twinmotion 2026.1 asks for macOS Sonoma 14.6.1, released in 2023 — a jump of six macOS major versions in roughly three and a half years of documentation, most of it landing in the same release that added native Apple Silicon support.

Minimum Mac requirements

macOS Sonoma 14.6.1 or later, an Apple Silicon M1 or M2 series chip (or an Intel processor with a PassMark single-thread score of 2,000 or higher, paired with a discrete card carrying 6 GB of VRAM), 32 GB of memory, and 30 GB of free disk space. Twinmotion can still run on older macOS releases, but Epic does not support them.

High-end Mac requirements

macOS Tahoe 26, an Apple Silicon M3 Max chip or better, and 64 GB of memory. Unlike Windows, where the high-end GPU option is expressed as a VRAM-and-benchmark figure any card can hit, the Mac high-end tier names a specific chip family. There is no discrete Mac GPU path at this tier the way there still is at the minimum.

What's not supported on Mac

One requirement is new and easy to miss: starting with Twinmotion 2026.1, Epic requires Xcode installed on the machine to run the application at all — 15.2 (15.4 recommended) at the minimum tier, 26.4.1 at the high-end tier. That is an unusual ask for a visualization tool rather than a development one, and it did not apply to earlier Twinmotion releases. It is easy to miss precisely because nothing about the Twinmotion install screen suggests a developer dependency is involved, and Apple does not install Xcode by default on a new Mac.

• The Path Tracer.Not available on Mac at any hardware spec. Twinmotion is built on Unreal Engine, and Epic states that Unreal Engine "does not yet support path tracing on macOS" — this is an engine limitation, not something a faster Mac fixes.
• VR mode.Not supported on Mac, which Epic attributes to "hardware and driver limitations on Macs."
• Lumen, at reduced quality.Lumen runs on Mac only in software ray tracing mode, which Epic warns "may impact visual quality" — and recommends the high-end configuration to offset it, on a feature that already has no hardware acceleration path on this platform.

What Twinmotion asks of the graphics card

The application-wide requirement is short: the latest available drivers, DirectX 11 or 12 support, and a VRAM figure that scales with tier — 6 GB minimum, 12 GB high-end. Epic measures the card itself against a PassMark G3D benchmark score rather than naming specific models: 10,000 or higher at the minimum tier, 20,000 or higher at the high-end tier. Intel ARC graphics cards are explicitly called out as not officially supported, and Epic recommends NVIDIA's Studio Drivers rather than Game Ready Drivers specifically for RTX 5090 owners.

The Path Tracer's separate, stricter floor

Twinmotion asks two separate questions of a graphics card, and only one of them is in the tier table above. The first is whether Twinmotion will run at all. The second, published on its own Path Tracer requirements page, is whether the Path Tracer specifically will run — and that answer is stricter and shaped differently. It is not a VRAM threshold any card can hit; it names architectures. To use the Path Tracer, Epic requires any NVIDIA RTX card, or an AMD RX 6000-series card or higher, with at least 8 GB of VRAM and DirectX 12 (DXR) support. NVIDIA T1000 cards are explicitly excluded by name, despite sharing the same Turing-generation ray-tracing hardware as early RTX parts.

Read the two pages together and the practical result is: a 6 GB GTX-class card clears Twinmotion's own minimum and never clears the Path Tracer's, no matter how the rest of the machine is specced. Nothing is broken if the Path Tracer option stays greyed out on hardware that otherwise runs Twinmotion fine — it is a second, separate floor, not a degraded version of the first one.

Twinmotion also supports multiple NVIDIA GPUs through SLI, which Epic says can improve Path Tracer performance "anywhere from 50% up to 200%" depending on the cards and the connection between them — but explicitly does not accelerate real-time Standard or Lumen rendering, and requires Windows 10 version 2004 or later to configure. Depending on the generation of NVIDIA cards involved, setting it up also means a physical bridge — an NVLink or SLI connector — between the two cards, not just two GPUs installed in the same case.

How much VRAM to buy, by what you render

Everything Epic asks for outside the graphics card is short and, compared to a BIM tool tracking a linked model, largely flat across tiers — the same disk figure, and requirements that scale with project size rather than with a discipline-specific file format.

CPU

Epic scores CPUs against PassMark's single-thread benchmark rather than an aggregate multi-core score — 2,000 or higher at the minimum tier, 2,500 or higher at the high-end tier. Because Twinmotion is a real-time, Unreal-Engine-based viewport rather than an offline batch renderer, the number that predicts how responsive it feels is clock speed on a single core, not how many cores the chip has.

RAM

16 GB at the Windows minimum, 64 GB at the Windows high-end. Mac asks for more at every tier — 32 GB minimum, 64 GB high-end — which means the Mac floor is double the Windows floor for hardware rated to do the same job. Nothing in Epic's documentation explains the gap; it has held since at least Twinmotion 2022.2, before Apple Silicon support existed.

Storage

30 GB of free disk space, unchanged across both tiers and both platforms. Epic notes that an SSD "can be a good choice if you work with very large projects" and that projects stored on one load and save faster, but does not publish a separate, larger figure for temp or cache files the way some rendering tools do at their high-end tier.

Unlike a vendor that republishes a dedicated requirements article for every yearly release, Epic keeps exactly two reference points live: the current specification page, and one archived page for Twinmotion 2022.2. There is no separately published spec page for 2023.1, 2023.2, 2024.1, 2024.2, 2025.1, or 2025.2 — searching for one returns nothing, and this page will not invent numbers to fill that gap. What can be stated with a source is below.

Two things fall out of that table. First, the high-end GPU benchmark bar rose by a third between the 2022.2 baseline and today — a PassMark G3D score of 15,000 was enough for the top tier then; 20,000 is the figure now. The minimum-tier GPU bar, by contrast, has not moved: 10,000 in 2022.2 and 10,000 in 2026.1. Second, the Mac floor and the Apple Silicon transition landed in the same release window — 2025.1 added native support, and by 2026.1 the minimum macOS version, the Xcode requirement, and the assumption that the GPU is Apple Silicon had all shifted with it.

Whatever release you land on, treat the file format as a one-way door. Twinmotion 2026.1's own release notes state it directly, and 2025.1's said the same thing a year earlier: a newer version opens projects saved in older ones, but "projects created and saved in [the new version] will not open in previous versions." Standardizing the whole team on an older release because one machine can't meet the current spec is a real option — reopening a file that has already been saved in the newer one is not.

The two-tier structure above maps onto real buying decisions faster than the raw spec sheet does. The question that actually separates these rows is not job title but whether the Path Tracer is part of the deliverable — that single feature moves a machine from a mid-range card to a specific architecture requirement no amount of extra RAM substitutes for.

Epic does not endorse specific laptop models, and neither does this page — no workstation SKU with a currently quotable price proved verifiable at the time of writing, so the bands below are approximate street prices for a comparable configuration, and the specifications are the part that holds.

Budget tier

Roughly $1,200 to $1,800. 16 GB of RAM, a discrete GPU with 6 GB of VRAM clearing the 10,000 PassMark G3D floor, and a fast single-thread CPU. This meets Epic's minimum tier and covers interior stills and single-building walkthroughs. No Path Tracer at this tier — an 8 GB RTX or RX 6000-series card is a different line item, not a software toggle.

Mid tier

Roughly $2,000 to $2,800. 32 GB of RAM and an 8–10 GB RTX-class card. This clears the Path Tracer's separate 8 GB VRAM and DirectX 12 floor as well as Twinmotion's own minimum, which is the more useful way to spend the budget than simply chasing the high-end VRAM figure.

Pro tier

$3,000 and up. 64 GB of RAM and a 12 GB-or-higher RTX card clearing the 20,000 PassMark G3D score — Epic's high-end tier, and the only configuration VR mode and 64K exports are rated for. For a Mac practice, the equivalent is an Apple Silicon M3 Max MacBook Pro or Mac Studio, which still never unlocks the Path Tracer or VR mode regardless of price.

Most of the reports that look like bugs are actually the app correctly enforcing one of the two separate hardware floors above — the general one and the Path Tracer's.

• Path Tracer option is missing or greyed out. Check the card against the Path Tracer's own requirements first — NVIDIA RTX or AMD RX 6000-series, 8 GB VRAM, DirectX 12 — before assuming the install is broken. A 6 GB GTX-class card that runs Twinmotion normally will never show this option.
• NVIDIA T1000 can't enable the Path Tracer. Expected. Epic excludes it by name even though it shares Turing ray-tracing hardware with early RTX cards.
• Intel ARC card flagged as unsupported. Epic states Intel ARC graphics cards are not officially supported, independent of their VRAM or benchmark score.
• Twinmotion won't install on a new Mac. From Twinmotion 2026.1 onward, Xcode has to be installed first — a requirement that did not exist on earlier releases and is easy to miss because Xcode is a developer tool, not something a rendering workflow would normally need.
• Multiple GPUs aren't speeding up real-time mode. Correct behaviour. Epic's SLI/multi-GPU support only accelerates the Path Tracer; Standard and Lumen rendering see no benefit from a second card.
• Lumen looks worse on Mac than on a Windows machine with a similar GPU. Also expected. Lumen only has a software ray tracing path on macOS — there is no hardware-accelerated Lumen on Mac at any spec.

None of these require new hardware. They are the difference between a machine that meets Epic's published spec and one that feels like it.

• Match the driver to the workload, not just the card. Epic specifically recommends Studio Drivers over Game Ready Drivers for RTX 5090 owners.
• Buy for the Path Tracer's floor, not just the app's. An 8 GB RTX or RX 6000-series card clears both requirements at once; a 6 GB card that only clears the general minimum will need replacing the moment the Path Tracer becomes part of the workflow.
• Keep large projects on an SSD.Epic's own guidance names this directly for load and save speed on projects approaching the 1 GB geometry threshold.
• Don't expect multi-GPU to help outside the Path Tracer. SLI/NVLink is a Path-Tracer-only performance feature; a second card bought for real-time Lumen work is spend without a payoff.
• Confirm DirectX 12 before relying on the Path Tracer.Twinmotion falls back to DirectX 11 automatically when a card doesn't meet the Path Tracer's requirements — check the setting in Preferences rather than assuming DX12 is active.

Every figure on this page exists because Twinmotion renders on the machine in front of you. Move the presentation image one step off that machine and the GPU floor, the VRAM figure, the driver version, and the Path Tracer's separate hardware test all go with it.

Render a House runs entirely in the browser, so it has no GPU requirement at all — not the app's 6 GB floor, and not the Path Tracer's stricter one. A screenshot of a Twinmotion viewport, or an exported still, works as an input; there is no native Twinmotion project file this or any browser tool opens directly. It is free to start, with 3 renders a day, and paid plans start at $39/mo.

The case where this matters most is exactly the one Twinmotion can never solve with better hardware: a Mac practice that wants a Path-Tracer-quality still. No Mac, at any spec, runs the Twinmotion Path Tracer — it is an engine limitation, not a benchmark one. Browser rendering does not have that ceiling, because it never asks the Mac's GPU to do the work at all.

What browser rendering cannot do

It is not a substitute for Twinmotion's real-time viewport, and treating it as one wastes time. Twinmotion's core value is Direct Link — live sync from Revit, SketchUp, ArchiCAD, and other source software, with instant feedback as the model changes. Browser rendering works from a static export or an image, so a change in the source model means exporting or uploading again. It also has no VR mode, no video timeline or walkthrough export, and no path-traced determinism you control frame by frame — it produces a still concept image, quickly, from geometry you already have.