About RigAtlas
Contact & corrections
RigAtlas is an independently run PC planning site. Questions and corrections go to the site operator.
Found an incorrect specification, a broken link or a problem with a guide? Send the page URL, the model or section, and what needs checking. You can also use this address for account and privacy questions.
Messages sent to this address are forwarded by Cloudflare Email Routing to the operator’s inbox and used to respond to your request.
How this content is prepared
RigAtlas publishes component reference information and planning guides. Component entries link to manufacturer sources and show their source-check dates. Guides explain the selection process and the documented checks available in this tool. Starter lists are planning examples; they are not claims of a physically assembled or benchmarked system.
For a purchase decision, use the manufacturer page for the exact model and revision. A catalog update date describes an editorial update, not a guarantee that every part is in stock or has been rechecked that day.
Product information
RigAtlas is a PC planning tool. The reference catalog links to manufacturer specifications. Compatibility guidance covers selected rules; always confirm BIOS support, revisions, mounting hardware and full assembly clearances. Power values are planning estimates, not measurements. No benchmark scores or frame rates are invented.
What the PC builder checks
RigAtlas helps you assemble a parts list, compare manufacturer specifications and investigate compatibility before buying. Choose parts in the studio or use the list view; both edit the same working draft. Sign in to save a configuration across devices.
The checks compare recorded specifications and model-specific evidence. A detected conflict is a reason to change or investigate the selection. A review notice means a condition still needs checking. Passing the available rules does not certify a complete build: undocumented revisions, mounting hardware, cable routing and firmware can still change the result.
- SSD interfaces and shared lanesCheck the exact M.2 slot, supported interface and disabled connections.
- Front USB-C connectionsMatch the case cable to the motherboard header and its supported speed.
- Graphics card and radiator clearanceCheck the configured case space, not only the advertised maximum GPU length.
How the power estimate works
The planning model adds the catalog CPU power rating, the selected GPU board power and a fixed 75 W allowance for the remaining components, then rounds up to the next 10 W.
10 × ceil((CPU watts + GPU watts + 75) ÷ 10)
Without a dedicated GPU, the calculation is available only when the selected CPU has recorded integrated graphics; that path adds no separate GPU power. Missing required ratings leave the estimate unavailable. The fixed allowance does not model every drive, fan or expansion card. CPU TDP is not maximum draw. This result is neither a wall-power measurement nor a recommended PSU wattage.
Use the PSU guide to check connectors, transient loads and manufacturer recommendations.
How local model memory is estimated
The local language-model tool calculates a theoretical weight-storage lower bound from the chosen parameter count and weight precision. It compares that value with the selected GPU’s verified dedicated memory and the installed system memory. It does not run the model or predict tokens per second.
Weight GiB = parameters in billions × 1,000,000,000 × bits ÷ 8 ÷ 1,073,741,824
| Parameter count | Weight lower bound |
|---|---|
| 8 billion | 3.73 GiB |
| 14 billion | 6.52 GiB |
| 32 billion | 14.90 GiB |
| 70 billion | 32.60 GiB |
For example, 8 billion parameters at 4 bits require a theoretical 3.73 GiB for weights alone. That does not mean a 4 GB card can run the model. Quantization metadata, buffers, activations, the KV cache and other applications also need memory. A named model’s actual parameter count and file format may differ from the rounded scenario.
Changing context length does not change the weight-only number in RigAtlas. Longer contexts can require more runtime memory, but this tool does not calculate a model-specific KV cache. A GPU with more memory than the lower bound therefore remains marked for review, not guaranteed to fit. System RAM and VRAM are not added together as one GPU memory pool.
Before buying, select the exact model file, quantization, context length, operating system and runtime. Check backend support and a runtime-specific memory estimate, then test the workload when possible. Image generation, training and fine-tuning need separate assessments.
- Hugging Face: model memory estimator and its inference limitations
- Ollama: context length and memory use
- LM Studio: estimate memory for a specific model with lms load
Method documented against the current tool and linked documentation on October 14, 2026. These are calculations and documented checks, not physical build tests.
Open your parts list and review the checks. Add a CPU and memory, then choose “Local language models” and expand “Adjust model size, precision and context” in the build review. Your existing draft is restored when browser storage is available.
Prices and affiliate links
When available, local quotes show official stores (brand direct or brand-authorized flagship stores) and the lowest third-party item price among connected stores. Each quote identifies its seller, currency and source update or feed-read time; shipping and tax details are shown separately. Missing or expired quotes remain unavailable. Price history appears only where permitted and uses actual observations of the same exact model, listing, seller and currency. Confirm final stock, delivery charges and taxes at the store.
Recorded prices are entered by the builder. Starter budgets are editable planning targets, not verified parts totals. Component budget tiers describe market positioning within a category. They are not live offers, and may exclude delivery, tax and import costs. The Buy at store action shows only configured affiliate model-search links for the selected component and destination. These searches do not verify an exact listing, stock or final price; confirm those details at the store. Latest prices and price history are separate from purchase links. If no affiliate purchase links are configured for that component and destination, purchase links remain unavailable. We may earn a commission from qualifying purchases through those links. Affiliate enrollment and rates vary by store and country.
Your information
Google sign-in gives RigAtlas a Google account identifier, your verified email address and your profile name. Account details, saved builds and sign-in sessions are stored in Cloudflare D1. Uploaded photos are stored in Cloudflare R2. We do not receive your Google password or store Google access or refresh tokens.
Private builds are restricted to your signed-in account. Anyone with an unlisted build’s link can open it; community builds appear in the gallery. Your chosen author name appears with published builds. We do not publish your account email. You can delete configurations from My builds and remove unused photos from your photo library. Signing out ends the current session.
RigAtlas uses secure cookies for sign-in and sessions. Sign-in requests expire after 10 minutes, and sessions last up to 30 days unless you sign out. The browser stores destination preferences and your temporary draft. Retailer-click counts contain the day, component, country and store, without an account identifier. Retailers apply their own privacy policies.
Advertising & privacy
Advertising is not currently enabled on this page.
When advertising is enabled, Google and other advertising partners may use cookies and device identifiers to serve, personalize and measure ads based on your previous visits to RigAtlas and other websites. Your consent choices and location affect how this information is used.
You can opt out of personalized advertising in Google ad settings.
Images and community
Starter images are for reference only. Refer to the linked store for actual product images. Upload only images you own or have permission to share. User descriptions are user-provided information and have not been independently tested. Starter builds and user photographs are labeled separately.