image_base64 metadata is generated only for documents or PDF pages that use High Res (not Fast or VLM) (#741)

Author: Paul-Cornell

ui/enriching/image-descriptions.mdx

@@ -39,6 +39,11 @@ Line breaks have been inserted here for readability. The output will not contain
 }
 ```
 
+<Note>
+    The `image_base64` field is generated only for documents or PDF pages that are [partitioned](/ui/partitioning) by using the High Res strategy. This field is not generated for 
+    documents or PDF pages that are partitioned by using the Fast or VLM strategy.
+</Note>
+
 For workflows that use [chunking](/ui/chunking), note the following changes:
 
 - Each `Image` element is replaced by a `CompositeElement` element.

ui/enriching/table-descriptions.mdx

@@ -43,14 +43,24 @@ Line breaks have been inserted here for readability. The output will not contain
 }
 ```
 
+<Note>
+    The `image_base64` field is generated only for documents or PDF pages that are [partitioned](/ui/partitioning) by using the High Res strategy. This field is not generated for 
+    documents or PDF pages that are partitioned by using the Fast or VLM strategy.
+</Note>
+
 Here are two examples of the descriptions for detected tables. These descriptions are generated with GPT-4o by OpenAI:
 
 ![Description of a table with information about endoscopic datasets](/img/enriching/Table-Description-1.png)
 
 ![Description of a table with information about potentiodynamic polarization of stainless steel](/img/enriching/Table-Description-2.png)
 
 The generated table's summary will overwrite any text that Unstructured had previously extracted from that table into the `text` field. 
-The table's original content is available in the `image_base64` field. 
+The table's original content is available in the `image_base64` field.
+
+<Note>
+    The `image_base64` field is generated only for documents or PDF pages that are [partitioned](/ui/partitioning) by using the High Res strategy. This field is not generated for 
+    documents or PDF pages that are partitioned by using the Fast or VLM strategy.
+</Note>
 
 For workflows that use [chunking](/ui/chunking), note the following changes:
 

ui/enriching/table-to-html.mdx

@@ -60,14 +60,17 @@ Line breaks have been inserted here for readability. The output will not contain
 }
 ```
 
+<Note>
+    The `image_base64` field is generated only for documents or PDF pages that are [partitioned](/ui/partitioning) by using the High Res strategy. This field is not generated for 
+    documents or PDF pages that are partitioned by using the Fast or VLM strategy.
+</Note>
+
 For workflows that use [chunking](/ui/chunking), note the following changes:
 
 - If a `Table` element must be chunked, the `Table` element is replaced by a set of related `TableChunk` elements.
 - Each of these `TableChunk` elements will contain HTML table output for only its own element.
 - None of the these `TableChunk` elements will contain an `image_base64` field.
 
-
-
 ## Generate table-to-HTML output
 
 import EnrichmentTableToHTMLHiResOnly from '/snippets/general-shared-text/enrichment-table-to-html-hi-res-only.mdx';

ui/summarizing.mdx

@@ -71,6 +71,11 @@ Line breaks have been inserted here for readability. The output will not contain
 }
 ```
 
+<Note>
+    The `image_base64` field is generated only for documents or PDF pages that are [partitioned](/ui/partitioning) by using the High Res strategy. This field is not generated for 
+    documents or PDF pages that are partitioned by using the Fast or VLM strategy.
+</Note>
+
 ## Summarize images or tables
 
 import EnrichmentImagesTablesHiResOnly from '/snippets/general-shared-text/enrichment-images-tables-hi-res-only.mdx';