diff --git a/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png b/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png
new file mode 100644
index 00000000000000..7bcfd3227adeda
Binary files /dev/null and b/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png differ
diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
index 51b5e0e93ea024..6e69a238131c4c 100644
--- a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
+++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
@@ -11,5 +11,7 @@ Cloudflare One administrators can now control which egress IP is used based on a
 - Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta.
 - During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
   - For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).
-  
+
+![Egress by FQDN and Hostname](~/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png)
+
 This will help apply egress IPs to your users' traffic when an upstream application or network requires it, while the rest of their traffic can take the most performant egress path.