S3 Chrome
trademark
S3 Graphics' Chrome series of graphics accelerators arrived in 2004 with the DeltaChrome line of chips. They were supplied as discrete, mobile, or integrated graphics.
Overview
In 2004 after the S3 Graphics company spun off their joint-venture with VIA, VIA attempted to re-launch the S3 Graphics brand with a new line of video cards under the name 'Chrome'. The Chrome range featured low power requirements and high-definition output making it attractive for small form factor scenarios and OEM systems. Unfortunately by the time Chrome released, the rapid progression of 3D gaming performance between rivals NVIDIA and ATI Technologies made S3's offerings uncompetitive in the lucrative high end consumer market.
The Chrome series supports Direct3D 9 with full pixel shader 2.0 support, excluding the unreleased Savage XP/AlphaChrome and early UniChrome. Later GPUs in the series offer Direct3D 10, 10.1, and 11 support, depending on the GPU.
S3's AcceleRAM technology allowed system RAM to be used to supplement the video card's RAM, and is similar to ATI's HyperMemory and NVIDIA's TurboCache. Chrome also introduced MultiChrome technology, allowing multiple matched Chrome cards to be used simultaneously in a system to increase graphics performance, similar to ATI CrossFire and NVIDIA's SLI.
Product Families
AlphaChrome
Unreleased - the first of the 'Chrome' product line, previously titled Savage XP and codenamed Zoetrope.
DeltaChrome
DeltaChrome added support for Shader Model 2.0, making it S3 Graphics' first released DirectX 9 product. Other features included the introduction of the Chromotion Video Engine, and dual 400 MHz DACs for multi monitor support.
Begin with the source’s own compact description: “S3 Chrome” is trademark. The dossier treats that line as a proposition to test through Chrome and trademark, not as a finished interpretation.
Why this record matters
The phrase “trademark” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Apr 29, 2026. The linked authority identifier is Q1041821. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2004.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “S3 Chrome”, its source revision and the description used here.
- Expand the search: follow S3 Chrome primary sources, S3 Chrome archive and Chrome research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “S3 Chrome”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “S3 Chrome” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.