diff --git a/content/chainguard/chainguard-images/features/ca-docs/faq.md b/content/chainguard/chainguard-images/features/ca-docs/faq.md
index e7855eb740..326bb5afe0 100644
--- a/content/chainguard/chainguard-images/features/ca-docs/faq.md
+++ b/content/chainguard/chainguard-images/features/ca-docs/faq.md
@@ -98,6 +98,12 @@ Custom Assembly provides the tools and defaults for secure image creation — bu
 
 {{< blurb/why_ca >}}
 
+## How do tags work for a custom assembly image (base image vs. added packages)?
+
+For a Custom Assembly image, the semantic tag (for example, `vX.Y.Z`) always reflects the version of the Chainguard container image on which it is based. Any added packages do not get their own version tags.
+
+When an added package is updated and available, your Custom Assembly image is rebuilt automatically and the new build that includes the updated package becomes the `latest` image. The semantic tag remains tied to the same base image digest until the base image itself is updated and a new semantic tag is created.
+
 
 ## Custom Assembly Troubleshooting
 Build failures can occur for a number of reasons, including the following: