Archicad 29 System Requirements: CPU, GPU, RAM, and the Redshift Contradiction

Graphisoft names four tiers, not the usual three — Minimum, Entry-level, Mid-range, and High-end — and ties CPU, RAM, graphics, and display together per tier rather than letting RAM float independently of the GPU.

Minimum: will it install

8 GB of RAM, a DirectX 11 compatible card of any capacity, and 5 GB of free disk space — the bare floor at which Archicad installs and opens, on an x64 multi-core Intel or AMD chip. Graphisoft doesn't attach a project-size ceiling to this row the way it does to the three tiers above it; it is a will-it-run line, not a will-it-work-well one.

Entry-level: small residential work

16 GB of RAM, a 4 GB VRAM DirectX 11 card, and an Intel Core i5 or AMD Ryzen 5 — Graphisoft's own starting point for a small residential project. This is also the tier a new Apple Silicon Mac buyer lands on by default, since Archicad's Mac Entry-level row names the base M1 chip.

Mid-range: everyday practice

32 GB of RAM, 6 GB of VRAM, and an Intel Core i7, Core Ultra 7, or AMD Ryzen 7. Graphisoft sizes this for everyday practice work rather than a named project size in megabytes, which is looser guidance than Autodesk gives for Revit.

High-end: large models and Redshift

64 GB of RAM or more, 8 GB of VRAM, and an Intel Core i9, Core Ultra 9, or AMD Ryzen 9. On paper this is the top of Graphisoft's own ladder. In practice it is also the exact VRAM figure Redshift asks for at minimum — a coincidence the section below works through in full.

Archicad has run natively on Apple Silicon since Archicad 25 in 2021, which puts it in different company from the other two heavyweight tools architects compare it against. Revit has no macOS build at all — Autodesk's only supported route is Windows inside Parallels. Lumion is Windows-only outright, and its own support team states that running it under Parallels or VMware Fusion "will cause crashes, glitches and License Key lock-ups." Archicad sidesteps both problems by shipping a real Mac build, not a workaround.

Minimum and recommended Mac configurations

Read the CPU row closely: every named tier above Minimum is Apple Silicon — M1, M2/M3/M4, M2 Max or M2 Ultra. An Intel Mac is only listed at the bare Minimum row, alongside 8 GB of RAM. That is Graphisoft treating Intel Macs as a legacy fallback rather than a configuration it still recommends buying.

What Graphisoft does not support on a Mac

• macOS 13 Venturais "installable but not supported" on Archicad 29 — it will run, but Graphisoft will not troubleshoot version-specific problems on it. macOS 14 Sonoma is the supported floor.
• NVIDIA hardware, at all.CUDA does not exist on macOS, so Redshift rendering on a Mac has exactly two paths: Apple Silicon itself, or an AMD card from the Navi or Vega generation onward. A Mac with an older AMD GPU or an Intel integrated chip clears Archicad's base spec but not Redshift's.
• A discrete VRAM number, on Apple Silicon. Apple's unified memory serves the CPU and GPU from the same pool, so the "16 GB" entry figure is total system memory, not a dedicated video-memory allocation the way the PC table's 4 GB VRAM line is.

Why the GPU matters for a BIM tool

Two different things inside Archicad ask the GPU for two different amounts of work. Modeling and documentation — walls, slabs, sections, the 3D window — are handled well within DirectX 11 on Windows or Metal on a Mac, and Graphisoft's own tier table never asks for more than 8 GB of VRAM for that side of the job. Rendering is the other side, and it is where the GPU stops being optional headroom and starts being the bottleneck.

NVIDIA vs AMD vs Apple silicon

Archicad ships two rendering engines, and they want opposite things from the GPU. CineRender, the CPU-based engine built on Cinema 4D's Physical Renderer, barely touches the graphics card — a machine at Graphisoft's Entry-level tier renders with it the same way a High-end machine does, just slower. Redshift, the GPU-accelerated engine Graphisoft added starting with Archicad 25, is the opposite: it needs a specific vendor and a specific architecture, not just a DirectX version. On Windows that means NVIDIA only — Graphisoft's dedicated Redshift-for-Archicad page names CUDA compute capability 5.0 as the minimum and 7.0 as recommended. On a Mac it means Apple Silicon or AMD — an M1 with 16 GB of RAM, or an AMD card from the Navi or Vega generation with 8 GB of VRAM or more. There is no card that satisfies both platforms' Redshift requirement at once, because the requirement itself is platform-specific.

VRAM: the silent bottleneck

VRAM is where a machine that "runs Archicad fine" and a machine that "renders in Archicad" stop being the same machine. Graphisoft's own PC tiers ask for 4, 6, and 8 GB of VRAM at Entry-level, Mid-range, and High-end. Redshift's own minimum on Windows is 8 GB, with 10 GB recommended — which means the Entry-level and Mid-range tiers Graphisoft sells Archicad against both sit below the floor its own renderer needs to switch on.

Which GPU to buy, by what you do in Archicad

CPU

Graphisoft names chip families per tier — Core i5/Ryzen 5 at Entry-level up to Core i9/Ryzen 9 at High-end, or M1 up to M2 Max/Ultra on a Mac — rather than a clock speed or a single-thread benchmark score the way Autodesk and Act-3D do for Revit and Lumion. That makes buying a CPU for Archicad a matter of matching a named tier, not calculating a PassMark threshold.

RAM

8 GB to install, 16 GB at Entry-level, 32 GB at Mid-range, 64 GB or more at High-end. Unlike Revit, Graphisoft does not publish a formula tying RAM to model size in megabytes — the tiers are named by project scale ("small residential," implicitly, up to "large or complex") rather than measured against a file-size figure you can check your own project against.

Storage

5 GB or more of free space, and that number has not moved on any of the five system requirements pages Graphisoft still hosts — Archicad 25 through Archicad 29 all state the same 5 GB minimum. NVMe SSD became the explicitly recommended drive type starting with Archicad 29; earlier versions recommended a SATA SSD at Entry-level and only asked for NVMe at Mid-range and High-end. The 5 GB figure is the application's own footprint — it does not budget for a project file, its backups, or its linked library, all of which grow well past it on a real job.

Internet and BIMcloud

Graphisoft's current requirements page states plainly that "fast internet access is essential for tasks such as connecting to a user's Graphisoft ID, using the License Manager Tool, accessing BIMcloud from a remote location, and downloading updates," without naming a minimum speed. Graphisoft's own Teamwork and BIMcloud community documentation describes the practical shape of that traffic instead of a single number: day-to-day editing sends and receives very little data, because BIMcloud's Delta Server technology syncs only what changed, but the moment a user joins a Teamwork project they download the entire model and its libraries at once — which is where a slow connection actually shows up. Graphisoft does not publish a single official Mbps figure on the pages checked for this article, so no number is quoted here as a minimum; treat the join-time download, not steady editing, as the bandwidth to plan around.

Archicad ships once a year. The table below is the official floor per release, useful both for "archicad 27 system requirements"-style lookups and for deciding whether an older machine matches an older, still-installed copy.

Two things hold steady across all five rows and one thing moved. The RAM figures — 16, 32, 64 GB — have been identical since Archicad 25 in July 2021; whatever else changed in four years of releases, Graphisoft's memory advice did not. The 5 GB storage minimum is equally unmoved. What did change is the graphics floor: Archicad 25 asked for OpenGL 4.5, Archicad 26 switched to DirectX 11 with a 2 GB VRAM entry point, and Archicad 27 raised that entry point to 4 GB, where it has stayed through 29.

If your hardware matches an older release rather than 29, the file format is the good news here, not the bad news. Archicad projects travel backward, one version at a time. Graphisoft's own support article on back-saving states that a file made in Archicad 28 can be saved directly as an Archicad 27 project through File > Save As; reaching Archicad 26 from there means opening that 27 file and saving it again as 26, with every intermediate version installed to make each hop. That is the opposite of Revit, where RVT has no save-to-older path at all and a file touched by a newer release is permanently locked out of the older one. A mixed-version Archicad team can still collaborate by stepping files down; a mixed-version Revit team cannot. The trade-off is real, though: back-saving needs a commercial licence rather than a trial, every intermediate version has to be installed on someone's machine, and Graphisoft warns that features introduced after the target version may not translate and should be checked post-save.

Look past the version table and Graphisoft's own pages disagree with each other on the exact question of what Redshift needs. The current, general system requirements page states it in one line: "To utilize the Redshift rendering engine, an NVIDIA graphics card with Cuda 7.0 or higher, or AMD's Navi/Vega is required." Read on its own, that makes CUDA 7.0 sound like the floor. Graphisoft's dedicated Redshift-for-Archicad page splits the same requirement by platform and by tier: on Windows, CUDA compute capability 5.0 is the stated minimum, and 7.0 is only the recommended figure — a full tier above what the general page implies is required. Two official Graphisoft pages name two different floors for the identical feature.

The practical version of the same gap sits in VRAM, and it is asymmetric by platform. On Windows, Archicad's own Entry-level tier (4 GB) and Mid-range tier (6 GB) both sit below Redshift's stated 8 GB minimum — only the High-end tier (8 GB) clears it, and even that falls short of the 10 GB Redshift recommends. A machine bought to Graphisoft's own "everyday practice" Mid-range spec runs Archicad correctly and cannot switch Redshift on. On a Mac, the same gap does not exist: Archicad's own Entry-level Mac configuration is already an Apple M1 with 16 GB of memory, which is exactly Redshift's stated Mac floor. A Mac buyer clears the render engine's requirement the moment they clear Archicad's own base spec; a Windows buyer has to skip two tiers past "Entry-level" to do the same.

Graphisoft does not endorse specific machines, and no laptop or desktop SKU price proved quotable from a primary source while researching this page, so what follows is the specification to buy against, with approximate price bands that move constantly and are not the durable part.

Budget tier

Roughly $1,000 to $1,500for a Windows machine with 16 GB of RAM and a 4 GB VRAM discrete GPU, or an entry Apple Silicon Mac with 16 GB of unified memory. Both clear Graphisoft's Entry-level tier and both are honest ceilings for CineRender-only work — Redshift is out of reach on the Windows side at this spec.

Mid tier

Roughly $1,800 to $2,600. 32 GB of RAM and a 6 GB VRAM card on Windows, or a mid-range Apple Silicon Mac (M2, M3, or M4) with 32 GB. Graphisoft's Mid-range tier, and still below Redshift's Windows VRAM minimum — the gap the section above covers in full.

Pro tier

$3,000 and up. 64 GB of RAM, an NVIDIA card with 8 to 10 GB or more of VRAM on Windows (the figure Redshift actually asks for), or a high-end Apple Silicon Mac (M2 Max or M2 Ultra) with 64 GB. Justified specifically by wanting Redshift switched on, not by model size alone — CineRender runs the same job on cheaper hardware, just slower.

• Redshift throws a CUDA or unsupported-device error. Almost always an AMD or Intel card on Windows — Redshift on Windows is NVIDIA-only, regardless of how much VRAM the card carries. On a Mac, check that the AMD card is Navi or Vega generation or newer; anything older is not supported either.
• Archicad runs, but Redshift renders are unavailable or greyed out. Check VRAM against the 8 GB Windows minimum before anything else. Graphisoft's own Entry-level and Mid-range PC tiers — 4 GB and 6 GB — both sit below it.
• Installer runs, but Graphisoft won't help with a bug. Check whether the OS is on the "installable but not supported" list — Windows 10 and macOS 13 Ventura both carry that label for Archicad 29.
• Ran out of disk space mid-project despite meeting the requirements. The published 5 GB figure is Archicad's own install footprint, not an allowance for a project file, its auto-backups, or a linked library — all of which routinely exceed it on a real job.
• Teamwork join is slow, even on a fast office connection. Expected behaviour, not a fault: joining a BIMcloud project downloads the entire model and its libraries once, which is the heaviest network moment Teamwork produces. Day-to-day editing after that point is comparatively light.

• Match the render engine to the hardware you already own. CineRender runs on any tier Archicad itself runs on. Only switch to Redshift once VRAM clears 8 GB on Windows, or the Mac clears Apple Silicon or a Navi/Vega AMD card — trying it below that spec just produces an error, not a slow render.
• Buy VRAM ahead of RAM if Redshift is the goal. Graphisoft's own Mid-range tier over-provisions RAM (32 GB) relative to the GPU (6 GB) for anyone planning to render with Redshift — the VRAM figure is the one that actually gates the feature.
• Give the project file room past the 5 GB minimum. That number is the application's footprint alone; budget separately for the model, its backups, and its library on the same drive.
• Schedule Teamwork joins outside peak office hours. The one moment BIMcloud saturates a connection is the full project download at join time, not routine editing afterward.
• Confirm the intermediate versions before back-saving a file. A one-hop save-down needs only the target version installed; multiple hops need every version in between, on some machine in the office.

Every GPU figure on this page exists because Archicad renders on your own machine. Move that one step off the machine and the VRAM floor, the CUDA compute-capability number, and the Windows-versus-Mac Redshift split all go with it.

That matters more here than it does for Revit or Lumion, because Archicad already solved the platform problem — it runs natively on the Mac either of those two doesn't. What Render a House removes instead is the render-engine gap: the many Archicad seats sitting at Graphisoft's own Entry-level or Mid-range tier, which run the software correctly and cannot switch Redshift on. It runs in a browser, needs no dedicated GPU, and has no CUDA or VRAM requirement to check. Archicad does not export GLB, GLTF, or OBJ directly, and a native PLN file will not open outside Archicad at all — export a BIMx model or an OBJ/GLB, or use a flat screenshot of an Archicad view, as the input. It is free to start, with 3 renders a day, and paid plans are $39/mo or $312/yr — full details are in the pricing docs.

What browser rendering cannot do

It is not a replacement for Archicad, and treating it as one wastes an afternoon. Browser rendering holds no BIM data — no walls, no schedules, no MEP model, no BIMcloud connection, and nothing that round-trips back into a PLN file. It will not produce construction documentation, a validated daylight study, or an animation, and it holds no live link to the model — a change in Archicad means exporting and uploading again, not watching an open scene update.

What it is good at is the single client-facing image, generated in seconds from geometry you already have, for the moment when standing up a full Redshift render is more setup than the deliverable is worth.

Pricing the licence as well as the machine? Archicad pricing covers what Graphisoft charges for Studio and Collaborate, and confirms both plans already bundle CineRender and Redshift at no extra cost. Revit pricing and Rhino pricing run the same numbers for the two BIM and modeling tools architects compare Archicad against most.

Sizing hardware for a different CAD or BIM seat in the same shortlist? Revit system requirements covers Autodesk's Windows-only equivalent, and Rhino system requirements covers the other tool that also ships natively for Mac and Windows alike. SketchUp system requirements and Blender system requirements cover the modeler most Archicad projects trade files with and the free alternative firms compare it against on cost.

Comparing the real-time and offline renderers Archicad studios add on top of the built-in engine? Enscape system requirements, Lumion system requirements, Twinmotion system requirements, and D5 Render system requirements cover the GPU floors for the four plug-in engines Archicad studios reach for most, and V-Ray system requirements covers the one renderer that has never shipped an Archicad edition at all. Enscape pricing, Lumion pricing, V-Ray pricing, and KeyShot pricing cover what each one costs on top of an Archicad seat.

Costing out the rest of a firm's toolchain? SketchUp pricing, Vectorworks pricing, and Chief Architect pricing cover the other BIM and CAD platforms architecture and design firms budget against Archicad, and Topaz AI pricing and Magnific AI pricing cover the AI upscalers studios pair with any of the render engines above. If all you need is to view an exported model rather than model or render it, the 3D model viewer opens a GLB, GLTF, or OBJ export in the browser with no Archicad licence required.