# AWS adds unified graphics images to WorkSpaces Applications > One image type can serve supported GPU families, with cross-family fleet changes available through the console or UpdateFleet API. Canonical URL: https://www.devobs.io/news/news-event-4da123a5ac4d130311e57863/ By: Claire Dubois Published: 2026-10-02T07:37:31.938Z Updated: 2026-10-02T07:37:31.938Z Event date: 2026-09-29 Section: Cloud AWS announced unified graphics images for Amazon WorkSpaces Applications on September 29, 2026. According to [the launch notice](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-workspaces-applications-unified-graphics-images/), the new image type works across all supported graphics instance families, including G4dn, G5, G6 and G7. Previously, each graphics generation required its own dedicated image, AWS says. ## Cross-family fleet changes When administrators create a fleet from a unified graphics image, the console displays compatible instance types. Fleets built on these images can also change instance types across supported families through the console or the `UpdateFleet` API. Previously, that operation was limited to changing sizes within one family, [according to AWS](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-workspaces-applications-unified-graphics-images/). For teams maintaining separate images by GPU generation, a common image could reduce duplicated application-packaging work and the number of parallel image lineages to maintain. Evaluating another supported GPU family would no longer necessarily require a separate generation-specific image. ## Availability and adoption paths AWS says unified graphics images are available in all AWS commercial and AWS GovCloud (US) Regions where WorkSpaces Applications graphics instances are supported. This availability statement should not be read as confirmation that every listed instance family is offered in every region. The [announcement](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-workspaces-applications-unified-graphics-images/) lists two starting points: upgrade an existing graphics image through Managed Image Update, or launch an image builder from a unified base image. ## Image compatibility is not workload validation Treat the shared image as an opportunity to consolidate packaging, not as a substitute for performance qualification. Before changing production fleets, validate application behavior, rendering output and workload-specific price-performance on each target family. The launch notice does not specify downtime for cross-family changes or promise identical application performance across GPUs. Plan the rollout rather than assuming that image compatibility makes the change disruption-free. ## Source references -