SolidsWorks

Choosing a computer for SOLIDWORKS: processor, RAM, graphics and storage

Start with a supported Windows configuration, 32 GB of RAM and an SSD. Compare rebuild, graphics and study results for the work the computer must do.

A cutaway aluminium bearing housing with red section faces in front of a dark desktop tower.

For SOLIDWORKS 2026, I'd start with a Windows 11 Pro computer, an x86_64 Intel or AMD processor, 32 GB of RAM, an SSD and a certified graphics configuration. That reaches the recommended memory level and gives you a supported platform before you spend more on speed. Choose the processor for rebuilding parts and drawings, then size the graphics and memory around the assemblies you work with.

A gaming label, a high core count or an RTX badge doesn't settle that choice. The useful evidence is the exact configuration on the certification list and a benchmark that measures the work you need it to do.

Start with the supported platform

The official system requirements give this baseline for SOLIDWORKS 2026. The 32 GB recommendation is a sensible starting point for a new modeling computer; 16 GB is the listed minimum.

ItemOfficial requirement or recommendationWhat to check on the order
WindowsWindows 11, 64-bit; Home editions and Windows To Go aren't supportedThe exact Windows edition, including any upgrade the seller must supply
Processorx86_64: Intel 64 or AMD64The processor architecture, then workload performance
Memory16 GB RAM; 32 GB recommendedInstalled capacity and the model's expansion options
GraphicsCertified cards and driversThe system, GPU, operating system, release and driver together
StorageSSD recommendedCapacity for Windows, software, working files and your backup arrangement

Windows 10 support ends with SOLIDWORKS 2025 SP5. A used computer advertised with Windows 10 therefore needs a supported Windows 11 configuration for a 2026 installation. The processor requirement also matters when shopping for a Windows Arm laptop: Arm isn't the x86_64 architecture listed here.

A Mac or virtual machine needs a separate compatibility decision. The requirements include specific hypervisor versions, while Boot Camp isn't supported. Follow the Mac and virtualization guide before treating a Mac as a substitute for this Windows workstation.

Buy processor performance for the task you repeat

The Performance Test's processor score covers rebuilds and drawing views, while its Simulation score measures a static study and can benefit from multiple processors. For a seat used mainly to design parts and assemblies, favor strong modeling and rebuild results. For simulation or rendering, compare the particular solver or rendering workload you will use.

I'd compare actual rebuild results before paying for a larger core count. GHz is useful within a processor's specifications, but it isn't a common performance score across different processor designs.

What two published test sets show

In Puget Systems' March 2026 tests, updated in April, the Core Ultra 7 270K Plus had a CPU composite score about 1% below the Ryzen 9 9950X3D. In the rebuild subtest, it tied the Ryzen 7 9850X3D and scored 3% above the Ryzen 7 9700X. Those are separate results, even within one test suite.

Puget used SOLIDWORKS 2024 SP5 and SPECapc 2024.1.13 at 4K, 150% scaling and full-scene anti-aliasing (FSAA), with an RTX PRO 5000 Blackwell. Its AMD and Intel platforms had different memory configurations. Use that comparison within those conditions.

BOXX's August 2026 workstation comparison used SPECapc for SOLIDWORKS 2025 with FSAA. Its three systems had 64 GB DDR5 and an RTX PRO 4000 Blackwell; the published composite scores were:

Tested workstation and processorCPU compositeGPU composite
APEXX S3, Core Ultra 9 285K1.842.22
APEXX A3, Ryzen 9 9950X3D2.012.26
APEXX T3, Threadripper 9980X2.252.18

Higher is better in both columns. The T3 led the CPU composite while the A3 led the GPU composite. A complete system affects the result, including a score named after the GPU.

CPU and GPU composite scores for three APEXX systems: the T3 leads CPU composite and the A3 leads GPU composite.
The highest CPU and GPU composite scores belong to different systems in this BOXX test set. The complete configuration and benchmark settings belong with the result.

These are two publishers' test sets, kept separate because their benchmark releases and settings differ. An average across them would obscure the choice. For everyday feature edits, take the rebuild subtest to the shortlist; for studies or rendering, ask for results from that workload. A composite lead alone doesn't establish that every operation is faster.

Verify the graphics configuration, not just the card name

The hardware certification list pairs a system model with an operating system, graphics card, SOLIDWORKS version and recommended driver. Match all of them. A seller's statement that a workstation range is certified leaves the configuration you are ordering unresolved.

  1. Get the complete computer model and the exact GPU from the quotation. Keep the model suffixes.
  2. Find the matching system and card for your SOLIDWORKS release and operating system.
  3. Read the Recommended Driver and Test Notes for that record. Save the record with the quotation.
  4. If the ordered configuration doesn't match, ask the seller or your SOLIDWORKS support provider to resolve it before purchase.
Five fields to match in a graphics certification record: system model, operating system, graphics card, SOLIDWORKS version and recommended driver.
Match the full configuration. A graphics-card name by itself leaves the system, software version and driver unchecked.

The list includes some integrated graphics configurations, so a separate card isn't a universal qualification rule. Equally, an RTX name or a large VRAM figure doesn't establish certification. For RealView Graphics, the Help requires a supported graphics card.

After support is settled, compare viewport results at the resolution and display style you use. Shaded models, shaded models with edges and RealView are different test conditions. A GPU rendering result from SOLIDWORKS Visualize answers a rendering question; it doesn't measure the time to rebuild a part.

Allow memory and storage for the largest job

Start a new modeling machine at 32 GB unless a known workload calls for more. For a large assembly, a study and other applications open together, check memory use on a representative machine before settling on capacity. More than 32 GB is a workload choice, rather than another universal minimum on the requirements page.

For example, a 32 GB configuration with a confirmed upgrade path gives you a way to respond when the projects grow. On a computer whose memory can't be expanded, the capacity you order is the ceiling. Ask the manufacturer about the exact model rather than assuming a laptop or desktop is upgradeable.

Choose an SSD for Windows, SOLIDWORKS and active files. Capacity is a separate decision: total the software and project storage you need, allow room to grow, and keep a backup plan. A fast local drive also doesn't establish the speed of a network share or PDM vault.

A laptop earns its place when the work travels

For a computer that stays at one desk, I'd shortlist desktops first because expansion and component replacement can matter over its working life. Confirm those options for the actual case and motherboard. Choose a laptop when you need the same files and tools away from the desk, then check its exact certified configuration, memory ceiling, ports and the displays it must drive.

A laptop processor's product name isn't a substitute for results from that laptop. Ask for a sustained workload comparison with the machine plugged in, using the settings you will use. Include the dock, external display and memory configuration in the quotation so the portable option is a complete purchase.

Keep the software budget separate. SOLIDWORKS license costs and conditions affect the total purchase, but they don't turn an unsupported hardware configuration into a supported one.

Check the computer you own before replacing it

Open SOLIDWORKS Rx from the Help menu, or choose Start > SOLIDWORKS Tools [version] > SOLIDWORKS Rx [version] in Windows. On Diagnostics, check the system and graphics-driver status. An internet connection is needed for that status; an error icon while offline doesn't establish a hardware fault. A current driver status doesn't establish that the machine has enough memory or speed for your job.

SOLIDWORKS Rx 2026 Diagnostics tab and the separate Benchmark to Start Benchmark route.
Select Diagnostics to check system and graphics-driver status. Use Benchmark > Start Benchmark for a performance test.

For a performance comparison, use the documented test sequence:

  1. Save your work, close applications and restart the computer.
  2. Before opening other applications, choose Start > SOLIDWORKS Tools [version] > SOLIDWORKS Performance Test [version].
  3. Read the instructions, click Start and follow the prompts. Keep other applications closed during the test.

Rx also provides Benchmark > Start Benchmark. Its results include elapsed times: graphics depends on both CPU and GPU, local I/O excludes network and PDM speed, and the Simulation result requires Simulation to be installed. Lower times are better; the SPECapc composite scores above use the opposite direction.

Four SOLIDWORKS benchmark choices connect rebuilds to processor time, model movement to graphics time, local file operations to I/O and a static study to Simulation.
Compare the category that matches the delay. These Rx results are elapsed times, so lower is better; local I/O does not measure network or PDM performance.

Keep the release, display settings, driver and power conditions with a result. After a change, repeat under the same conditions. The official hardware benchmarks page points to other comparisons, but a representative assembly should also inform whether an upgrade solves your own delay.

Put the intended release on the quotation

If you're buying for SOLIDWORKS 2027, reopen its system requirements and the certification record before ordering. A 2026 certification record doesn't by itself certify the next release, and virtual machines also need the hypervisor version listed for that release.

Keep the exact configuration, matching certification record and relevant benchmark with the order.