diff --git a/open-source/concepts/partitioning-strategies.mdx b/open-source/concepts/partitioning-strategies.mdx
index a578b480..e2ef8110 100644
--- a/open-source/concepts/partitioning-strategies.mdx
+++ b/open-source/concepts/partitioning-strategies.mdx
@@ -2,7 +2,7 @@
 title: Partitioning strategies
 ---
 
-import PartitioningStrategies from '/snippets/concepts/partitioning-strategies.mdx';
+import PartitioningStrategies from '/snippets/concepts/partitioning-strategies-oss.mdx';
 
 <PartitioningStrategies/>
 
diff --git a/platform-api/partition-api/partitioning.mdx b/platform-api/partition-api/partitioning.mdx
index a578b480..2d6ffbca 100644
--- a/platform-api/partition-api/partitioning.mdx
+++ b/platform-api/partition-api/partitioning.mdx
@@ -2,7 +2,7 @@
 title: Partitioning strategies
 ---
 
-import PartitioningStrategies from '/snippets/concepts/partitioning-strategies.mdx';
+import PartitioningStrategies from '/snippets/concepts/partitioning-strategies-platform.mdx';
 
 <PartitioningStrategies/>
 
diff --git a/snippets/concepts/partitioning-strategies.mdx b/snippets/concepts/partitioning-strategies-oss.mdx
similarity index 93%
rename from snippets/concepts/partitioning-strategies.mdx
rename to snippets/concepts/partitioning-strategies-oss.mdx
index c7dfe211..ff51e45f 100644
--- a/snippets/concepts/partitioning-strategies.mdx
+++ b/snippets/concepts/partitioning-strategies-oss.mdx
@@ -15,7 +15,6 @@ To give you an example, the `fast` strategy is roughly 100x faster than leading
 *   `fast`:  The "rule-based" strategy leverages traditional NLP extraction techniques to quickly pull all the text elements. "Fast" strategy is not recommended for image-based file types.
 *   `hi_res`: The "model-based" strategy identifies the layout of the document. The advantage of "hi_res" is that it uses the document layout to gain additional information about document elements. We recommend using this strategy if your use case is highly sensitive to correct classifications for document elements.
 *   `ocr_only`: Another "model-based" strategy that leverages Optical Character Recognition to extract text from the image-based files.
-*   `vlm`: Uses a vision language model (VLM) to extract text from these file types: `.bmp`, `.gif`, `.heic`, `.jpeg`, `.jpg`, `.pdf`, `.png`, `.tiff`, and `.webp`.
 
 **These strategies are available on the following partition functions:**
 
diff --git a/snippets/concepts/partitioning-strategies-platform.mdx b/snippets/concepts/partitioning-strategies-platform.mdx
new file mode 100644
index 00000000..36dcfa1f
--- /dev/null
+++ b/snippets/concepts/partitioning-strategies-platform.mdx
@@ -0,0 +1,18 @@
+
+For certain document types, such as images and PDFs, for example, Unstructured products offer a variety of different
+ways to preprocess them, controlled by the `strategy` parameter.
+
+PDF documents, for example, vary in quality and complexity. In simple cases, traditional NLP extraction techniques may
+be enough to extract all the text out of a document. In other cases, advanced image-to-text models are required
+to process a PDF. You can think of the strategies as being "rule-based" workflows (thus they are "fast"), or
+"model-based" workflows (slower workflow because it requires model inference, but you get "higher resolution", thus "hi_res").
+When choosing a partitioning strategy for your files, you have to be mindful of the quality/speed trade-off.
+To give you an example, the `fast` strategy is roughly 100x faster than leading image-to-text models.
+
+**Available options:**
+
+*   `auto` (default strategy): The "auto" strategy will choose the partitioning strategy based on document characteristics and the function kwargs.
+*   `fast`:  The "rule-based" strategy leverages traditional NLP extraction techniques to quickly pull all the text elements. "Fast" strategy is not recommended for image-based file types.
+*   `hi_res`: The "model-based" strategy identifies the layout of the document. The advantage of "hi_res" is that it uses the document layout to gain additional information about document elements. We recommend using this strategy if your use case is highly sensitive to correct classifications for document elements.
+*   `ocr_only`: Another "model-based" strategy that leverages Optical Character Recognition to extract text from the image-based files.
+*   `vlm`: Uses a vision language model (VLM) to extract text from these file types: `.bmp`, `.gif`, `.heic`, `.jpeg`, `.jpg`, `.pdf`, `.png`, `.tiff`, and `.webp`.
\ No newline at end of file