Chief Architect System Requirements 2026: X18's 16 GB Floor and the Card Ray Tracing Actually Needs

Minimum requirements

The Windows floor is 64-bit Windows 10 or 11, a multi-core processor, 16 GB of RAM, 5 GB of free disk space, and a video card with 4 GB of memory supporting DirectX 12 with Shader Model 6.0 or newer. Two exclusions are stated explicitly rather than implied: Snapdragon processors are not supported, which rules out the current wave of Windows-on-ARM laptops, and Intel integrated graphics is only accepted on 11th-generation or newer Intel processors.

That integrated-graphics allowance is unusually generous for software that renders. It means a mid-range office laptop with no discrete card is a supported configuration for drafting, and Chief Architect maintains a list of which Intel integrated GPUs qualify rather than leaving you to guess.

Recommended requirements

The recommendation is a different machine entirely: an Intel Core Ultra or AMD Ryzen 9 processor, 32 GB of RAM, a 1 TB SSD, and an NVIDIA GeForce RTX 5080 or AMD Radeon RX 7900. There is also a recommended screen size — 16 inches or more — which very few CAD vendors publish at all, and which is a real constraint if you were planning to work from a 13-inch laptop.

Why the gap between the two is so wide

The distance between a 4 GB DirectX 12 card and an RTX 5080 is larger than the equivalent gap on most spec sheets in this category. That is not sloppiness. The minimum describes what it takes to open plans, draw walls, place cabinets and orbit a 3D view. The recommendation describes what it takes to ray trace. The rest of this page is mostly about telling those two jobs apart before you spend money.

Mac minimum and recommended

The Mac requirements are shorter than the Windows ones because Chief Architect specifies a chip generation instead of a card. The floor is macOS Sequoia or Tahoe on an Apple M1 or newer, with 16 GB of RAM and 5 GB of disk. The recommendation is an Apple M5 or newer with 32 GB of RAM and a 1 TB SSD.

Apple Silicon, and where Intel Macs stopped

Chief Architect states that Intel processors and the A18 Pro and Neo are not supported. Reading that against the prior-versions page dates the cutoff precisely: X16 still listed a Mac video card requirement of "Apple M1 or newer, or an Intel or AMD GPU with support for Metal GPUFamily macOS 2", and X17 dropped the Intel and AMD half. So X16 is the last release an Intel Mac can run, and an Intel iMac or Intel MacBook Pro cannot be moved past it at any price. Chief Architect's compatible-Mac-models article restates the memory half of this for the current release: 16 GB of unified memory is a minimum, not a suggestion.

The ray-tracing footnote says nothing about Macs

Here is the gap worth knowing about before you buy a Mac. Chief Architect's ray-tracing footnote names its examples as the NVIDIA GeForce RTX series and the AMD Radeon RX series. Neither of those exists in an Apple Silicon Mac. The Mac requirement is a chip generation, M1 minimum and M5 recommended, and no Apple GPU is named as qualifying or not qualifying for the Physically Based technique.

The practical reading is that the M-series recommendation is doing the work the card recommendation does on Windows: if ray tracing is part of the job, buy toward the recommended chip rather than the minimum one. But the footnote itself gives a Mac buyer nothing concrete to check a specific machine against, and it is worth saying so rather than inventing a threshold Chief Architect has not published.

Every hardware page in this category has one section that actually decides a purchase, and on Chief Architect it is this one. The software has two different hardware floors and the requirements page states both without connecting them.

Floor one, running Chief Architect. A 4 GB DirectX 12 card, or Intel integrated graphics on an 11th-generation or newer chip. Plans open. Walls draw. The 3D camera orbits. Every drafting and documentation feature works.

Floor two, rendering in Chief Architect. The Physically Based and Clay techniques require a ray-tracing-compatible video card, and Chief Architect names the GeForce RTX and Radeon RX series as its examples. Intel integrated graphics is not in that class.

So a machine that Chief Architect fully supports — one that produces no warning, refuses no file, and satisfies every published minimum — can be structurally unable to make the image you show the homeowner. That is the trap. The integrated-graphics allowance reads like good news on a spec sheet and is exactly the configuration that cannot render.

If you are specifying a machine for someone else, the question to ask is not "does it meet the minimum". It is "do they need to produce renders". Those two questions have different answers and different price tags.

Why a plan drafter needs a GPU at all

Chief Architect is a 3D application wearing a floor-plan interface. Even while you are drawing in plan view it is maintaining a full 3D model of the building, and every camera view, elevation and cross section is generated from it. The GPU draws all of that. It also drives the Physically Based view, which is a real-time rendered mode rather than a still image, so the card is in the loop continuously rather than only when you press render.

What counts as a ray-tracing-compatible card

Chief Architect defines the class by example rather than by specification: a ray-tracing-compatible card "such as one from the NVIDIA GeForce RTX or AMD Radeon RX series". In practice that means a card with dedicated ray-tracing hardware — the RTX line from the 20 series onward, and Radeon RX from the 6000 series onward. Chief Architect does not publish a model-by-model list, so treat the series names as the guidance and check the specific card has ray-tracing acceleration before buying.

VRAM, and the one number that has moved

The published video-memory minimum is 4 GB, and it has been 4 GB since X15. Before that it was 2 GB, in X14 and X13. That is the only VRAM number Chief Architect publishes — there is no separate, higher figure for ray tracing, for large plans, or for the Physically Based view. The recommended cards carry far more than 4 GB, but Chief Architect recommends them by name rather than by capacity, so 4 GB remains the only stated threshold.

Recommended graphics cards by use case

The cost column is third-party street pricing and is approximate. Chief Architect publishes no hardware prices, and the only card figures it publishes at all are the two model names in its recommendation.

CPU: the generation floor, not the core count

Chief Architect's minimum is expressed as a processor generation, not a core count or a clock speed, and it exists mainly to bound which integrated graphics are acceptable. The generation floor has moved twice in five releases: Intel 6th generation for X13 through X15, 8th generation for X16, and 11th generation for X17 and X18. Anyone running a 2017 workstation on X15 hit a wall at X17 for reasons that have nothing to do with how fast the chip is.

The recommendation is an Intel Core Ultra or AMD Ryzen 9. Ray tracing and large plan regeneration are the two workloads that will use a stronger CPU; everyday drafting will not.

RAM: 16 GB is the floor, and it moved recently

16 GB minimum, 32 GB recommended. The minimum doubled at X16: X15 and every earlier version in the prior-versions table list 8 GB, and X16, X17 and X18 all list 16 GB. The recommendation has been 32 GB across every one of those releases, unchanged, which is a useful signal — Chief Architect raised the floor to meet reality rather than raising its ambition.

On a Mac the same 16 GB figure is unified memory shared with the GPU, so it is doing more jobs than 16 GB on a PC with a discrete card. That is the argument for treating 32 GB as the real target on Apple Silicon rather than a nice-to-have.

Storage: 5 GB to install, 1 TB to work

5 GB of free disk space installs the program. The recommendation is a 1 TB SSD, and the gap between those two numbers is the bonus catalogs, textures and manufacturer content libraries that make Chief Architect useful. The recommended figure was 512 GB in X13 and X14 and moved to 1 TB at X15, where it has stayed.

Display: a published minimum screen size

Chief Architect recommends a screen of 16 inches or more. Publishing a monitor recommendation at all is rare, and it is a reasonable one: the interface carries a plan, a library browser and a specification panel at the same time, and on a small laptop screen you spend the day closing panels to see the drawing.

This is the table to check before an upgrade, because two of the last three releases moved a floor that had nothing to do with speed — the Intel Mac cutoff at X17 and the RAM doubling at X16.

Three things fall out of reading it top to bottom. The RAM floor doubled once, at X16, from 8 GB to 16 GB. The VRAM floor doubled once, at X15, from 2 GB to 4 GB. And Intel Mac support ended at X17, which is the only one of the three that no amount of money fixes on an existing machine.

Chief Architect sells a professional product, Premier, and a consumer one, Home Designer. They are priced very differently. The published hardware requirements are identical.

Every row matches, down to the recommended card model and the ray-tracing footnote. That is worth knowing in both directions. If you are a homeowner buying Home Designer, you need the same 16 GB machine a professional needs — the cheaper licence does not come with a cheaper hardware bill. And if you are a firm standardising on a machine spec, one spec covers both products, so a support person on Home Designer and a designer on Premier can share a build sheet.

The pattern across all five rows: buy RAM to the recommendation rather than the minimum, and buy the card to the deliverable. RAM is the cheapest thing on the list and the one you cannot easily add to a laptop later. The card is the expensive decision and it only pays for itself if ray-traced output is something a client is paying for.

Chief Architect publishes no hardware prices, so the bands below are third-party street prices and are approximate. They are here to size a budget, not to quote one.

A supported drafting laptop — 11th-generation or newer Intel chip with integrated graphics, 16 GB of RAM, a 512 GB SSD and a 16-inch screen — lands roughly in the $900 to $1,300 band. It meets every published minimum and will not produce a Physically Based view.

A machine that renders starts where a ray-tracing card starts. Roughly $1,400 to $1,800buys a laptop with a 4060- or 5060-class card and 32 GB of RAM, which is the cheapest configuration that does both jobs. A desktop built to Chief Architect's own recommendation — Core Ultra or Ryzen 9, 32 GB, 1 TB SSD, RTX 5080 — sits closer to $2,600 to $3,400.

On the Mac side the decision is simpler because there is no card to choose. The minimum is any M1 or newer with 16 GB of unified memory; the recommendation is an M5 or newer with 32 GB. The step from 16 GB to 32 GB of unified memory is the upgrade worth paying for, because it is not user-installable afterwards.

The most common hardware message is "You are using a video card that does not meet the software's minimum requirements" . On a machine with both integrated and discrete graphics this usually means Chief Architect launched on the integrated GPU rather than the discrete one, which is a driver or power-profile setting rather than a genuine hardware failure. On a genuinely integrated machine, check the Intel processor generation first — 11th generation is the floor, and a 10th-generation chip will produce this message however much RAM it has.

Blank, black, flickering or torn 3D camera views are the other recurring class, and Chief Architect has a dedicated troubleshooting article for them. In most cases these are display-driver problems rather than capacity problems: the card clears the 4 GB requirement and the driver is out of date or is being overridden by a vendor control panel.

One case is genuinely a capacity problem and is worth separating out. If Physically Based or Clay views specifically fail while everything else works, that is the second floor from earlier in this page, not a bug — the card is doing its job and simply is not in the ray-tracing class.

The usual advice for old hardware is to stay on an older release. With Chief Architect that works, with one condition that catches people out: plan files only travel forward.

Chief Architect cannot open a plan that was created or last saved in a newer version, and it says so with a specific message when you try. There is no save-as-earlier-version command. So X17 can open an X16 plan, but the moment that plan is saved in X18 it stops opening in X17, and the X17 machine is locked out of it permanently.

There is one safety net. When a newer version saves a legacy file for the first time, Chief Architect writes an unaltered copy of the original into an Archives folder in its data directory, and that copy still opens in the version that made it. That protects the file you had; it does not let you move work backwards.

The other end of the range has its own cutoff. Chief Architect X9, Home Designer 2018 and newer read .plan and .layout files, but the older .pl and .laformats are no longer supported, per Chief Architect's legacy-files article. If you have archives in those formats, you need X8 or Home Designer 2017 to open them and re-save.

The practical rule for a mixed-version office: everyone upgrades together, or the person on the older version becomes read-only for any shared file.

Before buying anything, four settings move the needle more than a component swap.

Check which GPU the program launched on. On a laptop with switchable graphics this is the single most common cause of poor 3D performance, and it costs nothing to fix in the graphics control panel.

Work in a cheaper view. The standard rendered camera is far lighter than the Physically Based view. Keep the heavy mode for the moment you actually need it rather than leaving it on while you draft.

Turn off floors and layers you are not using. A 3D view rebuilds everything that is switched on, so a whole-house model with all floors visible costs more every time the camera moves.

Put the plan and the library on the SSD.Chief Architect's recommendation is a 1 TB SSD for a reason — the content libraries are large and get read constantly.

Being clear about the edges of this, because the two approaches are not substitutes.

A hosted render does not read a Chief Architect plan file. It reads the exported picture. Your material assignments, cameras, and anything outside the exported view do not travel.

It is not a Ray Trace replacement. A Ray Trace pass renders the exact design in the exact materials you specified. An AI render interprets. When a client is paying for a final image of a specific specification, ray tracing is the right tool and a card is the right purchase.

It does not lower Chief Architect's own floor. You still need 16 GB of RAM and a supported processor to run the software. Nothing here changes what it takes to draw the plan; it only changes what it takes to produce an image from one.

It will not fix a bad export. A cluttered, small, or badly framed view produces a poor render. The picture export dialog lets you set a large pixel size and clear Use Active Window Size — do both.

Chief Architect pricing covers what Premier and Home Designer cost per year and why neither is sold as a one-time purchase any more — the other half of the same budget conversation this page starts.

Chief Architect rendering walks through the picture-export workflow in full, including which view to export and what a render can and cannot infer from a plan.

Comparing hardware against another package on the same shortlist? SketchUp system requirements and Revit system requirements run the same numbers, and both have a two-floors problem of their own.

If the reason you are pricing a graphics card is client images rather than drafting speed, the architectural rendering tool is the cheaper end of that decision.