# Radeon RX 6700: the non-XT 10 GB capacity boundary

Radeon RX 6700: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.

Author: Retrivium team
Updated: 2026-11-02
Canonical URL: https://retrivium.ai/journal/amd-radeon-rx-6700-llm-rendering/
Language: en

The non-XT Radeon RX 6700 officially has 10 GB GDDR6 and a 175 W board specification. A 12 GB claim describes the different XT product, so losing the suffix immediately changes the workload budget.

## Official variants and the memory boundary

The table follows [AMD materials for this model](https://www.amd.com/en/products/graphics/desktops/radeon/6000-series/amd-radeon-rx-6700.html). It describes dedicated device memory, not system RAM. A “not verified” entry preserves a source gap; a neighboring configuration cannot supply the missing specification.

| AMD variant | Dedicated memory | Board power |
|---|---|---|
| [10 GB](https://www.amd.com/en/products/graphics/desktops/radeon/6000-series/amd-radeon-rx-6700.html) | 10 GB GDDR6 | 175 W |

## Establish the LLM software path

Radeon RX 6700 is absent from the checked [ROCm Core SDK 10.1.0 GPU list](https://rocm.docs.amd.com/en/docs-10.1.0/about/release-notes.html). Support for a neighboring model cannot be transferred through a shared generation or a similar name. For a separate experiment, the [llama.cpp build documentation](https://raw.githubusercontent.com/ggml-org/llama.cpp/master/docs/build.md) describes a Vulkan backend. That route requires a suitable driver, detection of the actual device, and validation of the selected GGUF; Vulkan in a specification does not establish that every operation works. Save tensor-placement logs and compare output with a reference run before concluding that the GPU is actually involved. This is not a claim of current official ROCm support for this card.

## A practical scenario for this model

A practical example is moving a conversation profile designed for RX 6700 XT onto the non-XT card. Confirm 10 GB and preserve the original context requirement first. Do not begin by silently lowering limits merely to start the engine. Load the same files, run a fixed request, and record which components actually reside on the GPU. If the profile fails, create an explicit alternative with changed placement or model representation. Each change needs its own reference-output comparison. That record can establish which parts of the original contract remain intact and which have changed. The shared RX 6700 name must not conceal capacity differences or turn a newly restricted profile into a claim that the old one works unchanged. Preserve the reason for every accepted adjustment.

## Validate Blender Cycles separately

RDNA 2 meets the HIP hardware floor in the [Blender Cycles 5.2 LTS manual](https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html): RDNA 1 or newer. This renderer requirement is independent of ROCm LLM support; validate the actual driver, build, and scene on the intended machine.

For a scene originally created on XT, compare resource contents before and after migration. Reducing texture resolution may produce a useful alternative, but it does not validate the original project on 10 GB.

## Preserve a machine-level acceptance record

The table gives AMD board-power specifications, not measured whole-computer consumption. Check the power supply, connectors, card dimensions, and airflow path for the actual system separately. Board power cannot establish inference speed.

Keep the complete non-XT name, 10 GB capacity, and alternative profile beside the original. This preserves the change rationale and prevents an incorrect preset returning during the next application installation.

The acceptance artifact should connect board identity, software versions, model revision, and the workload actually exercised. After any of those changes, the old result describes its original run rather than establishing compatibility of the new configuration.

## Related reading

[llama.cpp GPU layers: verify partial model offloading](/journal/llama-cpp-gpu-layers/); [Idle render farms: assessing a second GPU workload](/journal/render-farm-idle-gpus/); [NVIDIA and AMD GPU catalogue for LLM inference and server rendering](/journal/nvidia-amd-gpu-catalog/).