> ## Content Index > Fetch the complete content index at: https://solidsworks.com/llms.txt > Use this file to discover other available public pages before exploring further. # Choosing a computer for SOLIDWORKS: processor, RAM, graphics and storage - URL: https://solidsworks.com/solidworks-computer/ - Published: 2026-11-03T15:23:32.000Z - Updated: 2026-11-14T14:30:46.000Z - Description: 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. - Author: David Foster - Tags: Getting started For a new SOLIDWORKS modelling computer, I'd start with Windows 11 Pro on an x86\_64 Intel or AMD processor, 32 GB of RAM, an SSD and a graphics configuration certified for the intended release. That meets the [recommended memory level and supported platform requirements](https://www.solidworks.com/support/system-requirements?ref=solidsworks.com) before you pay for extra speed. Spend the next part of the budget on the operation that keeps you waiting: rebuilding, moving the model, solving a study or rendering an image. My first question is what happens after a design change. A slow feature rebuild, a jerky assembly view and a long render need different comparisons; a high core count or an RTX badge cannot answer all three. ## Match the computer to the work | What makes you wait? | Evidence to prioritise | Before spending more | | ------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Changing a dimension, rebuilding features or updating drawing views | CPU rebuild and drawing results from a comparable SOLIDWORKS test | Check which feature or assembly relationship causes the delay | | Rotating, zooming or displaying an assembly | Viewport results at your resolution, anti-aliasing and display style | Match the certified system, GPU, driver and release; check image quality | | Opening or saving files | Local storage results, or a separate network/PDM diagnosis | Find where the files and references are being read | | Meshing or solving a Simulation study | The particular solver, study size and memory demand | Use a representative study rather than a modelling score | | Producing a Visualize image | The selected renderer, render mode, GPU support and scene memory | Confirm the engine's GPU and driver requirements | The [SOLIDWORKS Performance Test](https://help.solidworks.com/2026/english/SolidWorks/sldworks/t%5Fbenchmarking%5Fhardware.htm?ref=solidsworks.com) makes similar distinctions: processor work includes rebuilds and drawing views, graphics depends on both CPU and GPU, and local I/O excludes network and PDM speed. Its Simulation result uses a static study. It isn't a forecast for every analysis you might run. ## Settle support before comparing speed The [system requirements](https://www.solidworks.com/support/system-requirements?ref=solidsworks.com) list 16 GB RAM as the minimum and 32 GB as recommended for native SOLIDWORKS Design. They recommend an SSD and certified graphics cards and drivers. The separate PDM Contributor/Viewer and Electrical Schematic memory row is not the specification for a full modelling seat. Check the Windows edition as well as the version. Windows Home and Windows To Go aren't supported. Windows 10 support ends at SOLIDWORKS 2025 SP5, so an older Windows 10 workstation needs a supported Windows 11 configuration for a 2026 installation. A Windows Arm laptop does not match the listed Intel 64/AMD64 architecture. Put the actual SOLIDWORKS release on the order. A 2026 certification does not establish support for 2027\. Mac and virtual-machine choices also need the listed hypervisor and operating-system versions; Boot Camp isn't supported. The [Mac compatibility guide](https://solidsworks.com/solidworks-mac/) covers that separate decision. ## Choose the processor by its rebuild result For a seat used mainly to create parts, assemblies and drawings, I'd shortlist CPUs from rebuild results before paying for more cores. The [official processor-test explanation](https://help.solidworks.com/2026/english/SolidWorks/sldworks/t%5Fbenchmarking%5Fhardware.htm?ref=solidsworks.com) says extra processors or cores do not improve this processor score much because most of the operations use one CPU. Clock speed is one specification, but GHz does not provide a common performance scale across different processor designs. ### A composite winner can lose the relevant subtest [Puget Systems' March 2026 engineering tests](https://www.pugetsystems.com/labs/articles/intel-core-ultra-200s-plus-engineering-review/?ref=solidsworks.com), updated in April, show why the subtest matters. These are selected results from one test series; higher scores are better. | Tested processor | CPU composite | CPU rebuild | | ---------------------------- | ------------- | ----------- | | AMD Ryzen 9 9950X3D | 3.46 | 3.15 | | Intel Core Ultra 7 270K Plus | 3.41 | 3.18 | | AMD Ryzen 7 9850X3D | 3.06 | 3.18 | | AMD Ryzen 7 9700X | 2.90 | 3.09 | The 9950X3D led this selection's composite, while the 270K Plus and 9850X3D tied in rebuild. Their 3.18 rebuild score was about 2.9% above the 9700X's 3.09\. That's a score difference in this test, not a promise that every editing session will finish 2.9% sooner. I'd compare complete quotes and a representative project before paying a large premium for that margin. 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. The AMD systems had 64 GB DDR5-5600; the Intel platforms had 48 GB, with different memory speeds. Treat these as tested platform results, not isolated CPU measurements. A separate [DEVELOP3D comparison published in February 2025](https://develop3d.com/workstations/amd-ryzen-9000-vs-intel-core-ultra-200s-series-processors/?ref=solidsworks.com) makes the same buying question concrete: the Ryzen 9 9950X scored 2.67 in rebuild against the Ryzen 7 9800X3D's 2.57, but 2.36 in mass properties against 3.04\. Higher is better in both. That series used SOLIDWORKS 2022 and the [now-retired SPECapc for SOLIDWORKS 2022 benchmark](https://www.spec.org/products/fairuse/specapc%5Ffor%5Fsolidworks/?ref=solidsworks.com), with different complete systems. It is historical evidence of operation-dependent rankings, not a current-release speed forecast or a set to average with Puget's scores. ## Check certification, then compare your viewport mode The [hardware certification list](https://www.solidworks.com/support/hardware-certification/?ref=solidsworks.com) identifies the system model, operating system, graphics card, SOLIDWORKS release, recommended driver and Test Notes. Match that complete record to the quotation. A workstation range's certification badge doesn't confirm every configuration sold under its name. 1. Get the exact computer model and graphics card, including model suffixes. 2. Find the matching system, operating system and SOLIDWORKS release in the certification list. 3. Read the **Recommended Driver** and **Test Notes**. Keep the matching record with the order. 4. Ask the seller or your SOLIDWORKS support provider to resolve any mismatch before purchase. The list includes some integrated graphics configurations. A separate card is therefore not a universal qualification rule, just as an RTX name or a large VRAM figure isn't proof of certification. [RealView Graphics requires a supported card](https://help.solidworks.com/2026/english/SolidWorks/sldworks/c%5Frealview%5Fgraphics.htm?ref=solidsworks.com); it adds real-time surface shading, reflections and self-shadows. It is a viewport feature, with a different job from Visualize rendering. ### RealView changes this GPU comparison In [Puget's April 2026 Arc Pro B70 review](https://www.pugetsystems.com/labs/articles/intel-arc-pro-b70-review/?ref=solidsworks.com), the ordering of these two cards reverses when RealView is enabled. The page was modified in July; the published scores remain one test series. Higher is better. | Tested graphics card | Shaded score | Shaded RealView score | | ----------------------------- | ------------ | --------------------- | | Intel Arc Pro B70 | 3.12 | 5.43 | | NVIDIA RTX PRO 2000 Blackwell | 3.29 | 3.18 | [![Arc Pro B70 and RTX PRO 2000 Blackwell score 3.12 and 3.29 in Shaded, and 5.43 and 3.18 in Shaded RealView.](https://storage.ghost.io/c/4c/fc/4cfc073a-f190-4bcc-b2ab-759be23dfa61/content/images/2026/11/gpu-mode-v1.webp)](https://storage.ghost.io/c/4c/fc/4cfc073a-f190-4bcc-b2ab-759be23dfa61/content/images/2026/11/gpu-mode-v1.webp?ref=solidsworks.com) Compare the display mode you use: the same two cards change order when RealView is enabled. Both panels use the same score scale. The RTX PRO 2000 Blackwell led ordinary Shaded, while the B70 led Shaded RealView. These are SPECapc scores, not frames per second. I'd use the result for my display style to narrow the shortlist, then check the exact certified system and driver. This run used SOLIDWORKS 2024 SP5, SPECapc 2024.1.13, 4K and FSAA on a Ryzen 9 9950X3D system with 64 GB DDR5-5600 and Windows 11 Pro. Intel used driver 101.8515 and NVIDIA 595.71\. A benchmark driver is part of that result; the recommended driver in your certification record is a separate check. These scores do not establish performance at every resolution or on a different laptop carrying a related GPU name. ## Size Simulation and Visualize separately If solving studies is the long part of your day, request results for the solver and study type you use, with a comparable mesh and enough RAM to complete it. A CPU rebuild score measures a different operation. The Performance Test's static-study result can help compare that test, but it doesn't establish how every solver scales with cores. For Visualize, first choose the renderer and mode. The [Visualize 2026 requirements](https://help.solidworks.com/2026/english/visualize/c%5Fviz%5Fprereqs%5Fsystem%5Freqs.htm?ref=solidsworks.com) distinguish Stellar Accurate, Stellar Fast and AMD ProRender: Stellar Accurate lists NVIDIA Maxwell or later, while Stellar Fast lists NVIDIA Turing with RT cores or AMD RDNA2 or later. The page gives the applicable driver and video-memory requirements for each engine. Don't buy a GPU from a native-CAD viewport chart and assume it is the right rendering configuration. Ask for a representative scene at the output quality you need. Keep the renderer, mode, resolution, driver and GPU memory with the result, and compare it with the same settings on the alternative system. ## Choose memory and storage from the largest working job 32 GB is my starting point for a new modelling seat because it is the official recommendation. Moving to 64 GB or more should answer a known memory demand: your largest assembly, study or render scene with the other applications you need open. There is no reliable universal conversion from assembly component count to RAM; detailed geometry, configurations and study data change the demand. On a representative computer, watch memory during the whole job, including the solve or render, rather than only after opening the file. [Task Manager monitors memory, CPU and disk activity](https://support.microsoft.com/en-us/windows/experience/system-configuration-tools-in-windows?ref=solidsworks.com); open it with **Ctrl + Shift + Esc**. If the job approaches the installed capacity or becomes unresponsive, record what happens and check it with support before treating a RAM upgrade as the complete diagnosis. Get the exact memory ceiling and upgrade route from the manufacturer. A desktop may have spare slots, or a laptop may have replaceable modules, but neither follows automatically from the form factor. With soldered memory, the capacity you order may be the capacity you keep. Use an SSD for Windows, SOLIDWORKS and active local files. Decide capacity by adding the software, projects, study data and space for growth; keep a separate backup arrangement. If opening or saving is slow from a network share or PDM vault, investigate that path. The official local-I/O test does not measure it, so an NVMe upgrade alone doesn't settle the cause. ## Desktop, laptop or an existing workstation? For a computer that stays at one desk, I'd shortlist desktops first because expansion and component replacement can extend their useful life. Confirm the options for the actual motherboard, case and power supply. For work that travels, choose a laptop and compare a sustained run on that exact model, plugged in with the power settings you will use. A mobile CPU or GPU name doesn't establish the performance of its desktop counterpart. Include the dock, external displays, ports and memory configuration in the quote. Ask whether the exact laptop configuration appears in the certification list; a related desktop entry isn't a substitute. For a student purchase, check the course's software release, projects and available laboratory or remote access before spending the budget. A used workstation can be a sensible quote to examine, but verify Windows 11 support, the relevant certification record, memory expansion and the seller's warranty. An old professional label does not make it suitable for the next course or release. The [student access guide](https://solidsworks.com/solidworks-for-students/) covers the software entitlement separately. ## Diagnose the delay before replacing the computer First record what you have. In Windows, right-click **Start > Settings > System > About** for the processor, installed RAM, system type and Windows details. Microsoft also documents [the storage view under System > Storage](https://support.microsoft.com/en-us/windows/experience/find-information-about-your-windows-device?ref=solidsworks.com). Compare these with the requirements for your intended SOLIDWORKS release. Open [SOLIDWORKS Rx from the Help menu](https://help.solidworks.com/2026/english/SolidWorks/Sldworks/c%5FSOLIDWORKS%5FRx.htm?ref=solidsworks.com), or use **Start > SOLIDWORKS Tools \[version\] > SOLIDWORKS Rx \[version\]**. On **Diagnostics**, check the system and graphics-driver status. An internet connection is needed for that status, so an offline error icon isn't proof of a hardware fault. Then inspect the file. [Tools > Evaluate > Performance Evaluation](https://help.solidworks.com/2026/english/SolidWorks/sldworks/HIDD%5FASSEM%5FSTATS%5FDLG.htm?ref=solidsworks.com) separates assembly open, display, rebuild and settings checks. It can identify excessive image quality, graphics triangles, mates, in-context relationships or flexible subassemblies. Its warnings are recommendations, not errors: review the design intent before changing the model to improve a score. For a part, [Performance Evaluation lists each feature's rebuild time](https://help.solidworks.com/2026/english/SolidWorks/sldworks/HIDD%5FFEATURE%5FREPORT.htm?ref=solidsworks.com). That helps distinguish one expensive feature from a general shortage of processor speed. Work on a copy if you suppress or simplify features as a comparison. ### Use a repeatable comparison 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 run. 4. Record the SOLIDWORKS release, driver, display settings and power conditions with the results. Repeat under the same conditions after a change. The [documented test](https://help.solidworks.com/2026/english/SolidWorks/sldworks/t%5Fbenchmarking%5Fhardware.htm?ref=solidsworks.com) reports elapsed times, so lower is better. Rx also offers **Benchmark > Start Benchmark**. The Simulation result requires Simulation to be installed. Keep these timings distinct from the higher-is-better SPECapc scores above. ## Validate a quote with a real design change Ask the supplier to run a copy of a representative project on the quoted configuration. Choose a change that exposes the work you do: alter a driving dimension, rebuild the part and assembly, update the drawing, then rotate the model in your usual display mode. Include a study or render only if it belongs to that seat's work. Check that the files remain correct as well as recording the waiting time. Keep these details with the purchase: - The complete system, CPU, RAM capacity and expansion limit, GPU, SSD capacity and Windows edition. - The intended SOLIDWORKS release and matching certification record, recommended driver and Test Notes. - The operation measured, project or benchmark version, display and power settings, and result. - The included displays or dock, warranty and support arrangement, plus the software licence budget. I'd approve the system that shortens the relevant wait and preserves a supported working configuration. That is a stronger reason to buy than a general “best for SOLIDWORKS” badge.