diff --git a/docs/articles/test-workflows-step-output-transfer.md b/docs/articles/test-workflows-step-output-transfer.md
new file mode 100644
index 000000000..66f4e52f7
--- /dev/null
+++ b/docs/articles/test-workflows-step-output-transfer.md
@@ -0,0 +1,97 @@
+# Transferring Output Between TestWorkflow Steps
+
+Testkube TestWorkflows execute steps sequentially, and each step runs in its own container context. To pass data between steps, you need to use persistent storage mechanisms that survive across step boundaries.
+
+## Methods for Transferring Output
+
+### 1. File-Based Output Transfer
+
+The most common and reliable approach is to write output to files in the first step and read them in the second step:
+
+```yaml
+apiVersion: testworkflows.testkube.io/v1
+kind: TestWorkflow
+metadata:
+  name: example-output-transfer
+spec:
+  steps:
+    - name: Generate data
+      shell: |
+        # Generate some output and save to file
+        echo "Hello from step 1" > /data/output.txt
+        echo "Additional data" >> /data/output.txt
+        
+    - name: Process data
+      shell: |
+        # Read the output from previous step
+        content=$(cat /data/output.txt)
+        echo "Processing: $content"
+        # Process the data further...
+```
+
+### 2. Using the `file()` Function in Expressions
+
+You can use the `file()` function to read file contents in expressions:
+
+```yaml
+apiVersion: testworkflows.testkube.io/v1
+kind: TestWorkflow
+metadata:
+  name: example-file-expression
+spec:
+  steps:
+    - name: Generate configuration
+      shell: |
+        echo '{"apiUrl": "https://api.example.com", "timeout": 30}' > /data/config.json
+        
+    - name: Use configuration
+      shell: |
+        # The file content is available via expressions
+        config='{{ file("/data/config.json") }}'
+        echo "Using config: $config"
+```
+
+### 3. Using Artifacts for Complex Data Transfer
+
+For more complex data or when you need to preserve the output for later use:
+
+```yaml
+apiVersion: testworkflows.testkube.io/v1
+kind: TestWorkflow
+metadata:
+  name: example-artifact-transfer
+spec:
+  steps:
+    - name: Generate data
+      shell: |
+        mkdir -p /data/output
+        echo "Step 1 output" > /data/output/step1.txt
+        echo "More data" > /data/output/data.json
+      artifacts:
+        paths:
+          - "/data/output/**/*"
+          
+    - name: Process data
+      shell: |
+        # Access the artifacts from previous step
+        if [ -f /data/output/step1.txt ]; then
+          content=$(cat /data/output/step1.txt)
+          echo "Processing: $content"
+        fi
+```
+
+## Key Points to Remember
+
+1. **File System Persistence**: Files written in one step are available in subsequent steps within the same workflow execution.
+
+2. **Working Directory**: By default, steps run in `/data/repo` or `/data` directory, so use absolute paths like `/data/output.txt` for reliable file access.
+
+3. **Expressions**: Use `{{ file("/path/to/file") }}` to read file contents in expressions and configuration.
+
+4. **Artifacts**: Use artifacts to preserve and share complex data structures between steps.
+
+5. **Environment Variables**: Environment variables set in one step are not automatically available in subsequent steps unless explicitly saved to files.
+
+6. **JSON Data**: For structured data, consider using JSON format and the `jq` command for parsing.
+
+7. **Error Handling**: Always check if files exist before trying to read them in subsequent steps.
diff --git a/sidebars.js b/sidebars.js
index 07284d2fd..2553f391b 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -435,6 +435,11 @@ const sidebars = {
                   label: "Local Dev Loop",
                   id: "articles/local-dev-loop",
                 },
+                {
+                  type: "doc",
+                  label: "Transferring Output Between Steps",
+                  id: "articles/test-workflows-step-output-transfer",
+                },
               ],
             },
           ],