diff --git a/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/index.md b/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/index.md
index 7e554dabac1..6ffc61eff85 100644
--- a/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/index.md
+++ b/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/index.md
@@ -39,6 +39,8 @@ In any other connector, extracting metadata happens automatically. In this case,
 metadata from buckets, but in order to understand their internal structure we need users to provide an `openmetadata.json`
 file at the bucket root.
 
+`Supported File Formats: [ "csv",  "tsv", "avro", "parquet", "json", "json.gz", "json.zip" ]`
+
 You can learn more about this [here](/connectors/storage). Keep reading for an example on the shape of the manifest file.
 
 {% partial file="/v1.3/connectors/storage/manifest.md" /%}
diff --git a/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/yaml.md b/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/yaml.md
index 237f6d86c38..376486685a9 100644
--- a/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/yaml.md
+++ b/openmetadata-docs/content/v1.3.x/connectors/storage/gcs/yaml.md
@@ -42,6 +42,8 @@ In any other connector, extracting metadata happens automatically. In this case,
 metadata from buckets, but in order to understand their internal structure we need users to provide an `openmetadata.json`
 file at the bucket root.
 
+`Supported File Formats: [ "csv",  "tsv", "avro", "parquet", "json", "json.gz", "json.zip" ]`
+
 You can learn more about this [here](/connectors/storage). Keep reading for an example on the shape of the manifest file.
 
 {% partial file="/v1.3/connectors/storage/manifest.md" /%}
diff --git a/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/index.md b/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/index.md
index 64aea99eaa2..d89634923ab 100644
--- a/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/index.md
+++ b/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/index.md
@@ -39,6 +39,8 @@ In any other connector, extracting metadata happens automatically. In this case,
 metadata from buckets, but in order to understand their internal structure we need users to provide an `openmetadata.json`
 file at the bucket root.
 
+`Supported File Formats: [ "csv",  "tsv", "avro", "parquet", "json", "json.gz", "json.zip" ]`
+
 You can learn more about this [here](/connectors/storage). Keep reading for an example on the shape of the manifest file.
 
 {% partial file="/v1.4/connectors/storage/manifest.md" /%}
diff --git a/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/yaml.md b/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/yaml.md
index 4a2d28af333..b950b270f3f 100644
--- a/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/yaml.md
+++ b/openmetadata-docs/content/v1.4.x-SNAPSHOT/connectors/storage/gcs/yaml.md
@@ -42,6 +42,8 @@ In any other connector, extracting metadata happens automatically. In this case,
 metadata from buckets, but in order to understand their internal structure we need users to provide an `openmetadata.json`
 file at the bucket root.
 
+`Supported File Formats: [ "csv",  "tsv", "avro", "parquet", "json", "json.gz", "json.zip" ]`
+
 You can learn more about this [here](/connectors/storage). Keep reading for an example on the shape of the manifest file.
 
 {% partial file="/v1.4/connectors/storage/manifest.md" /%}