diff --git a/docs/user-guide/creating-application/workflow/file-upload-during-build.md b/docs/user-guide/creating-application/workflow/file-upload-during-build.md
new file mode 100644
index 0000000000..c15aeebe03
--- /dev/null
+++ b/docs/user-guide/creating-application/workflow/file-upload-during-build.md
@@ -0,0 +1,194 @@
+---
+canonical: https://docs.devtron.ai/docs/user-guide/creating-application/workflow/file-upload-during-build
+meta-description: Learn how to configure a File type input variable in a Pre-Build or Post-Build task so that users must upload a file when triggering a CI pipeline build in Devtron.
+---
+
+# File Upload During Build Time
+
+:::info Who Can Perform This Action?
+- **Uploading a file at build trigger time** — Users with **Build and Deploy** permission and above on the application.
+- **Configuring the File variable in a pipeline** — Users with **Admin**, **Manager**, or **Super Admin** permission on the application.
+:::
+
+## Introduction
+
+When running scripts in a Pre-Build or Post-Build stage, your pipeline may require a file — such as a `.env` file, SSL certificate, license key, or environment-specific configuration — that should not be committed to your Git repository.
+
+Devtron supports a **File** type input variable inside **Execute custom task**. When configured, this variable:
+
+- Mounts the uploaded file inside the build container at a path you define (e.g., `/devtroncd`).
+- Blocks the build at trigger time until the file is uploaded, if the variable is marked as **required** and **Ask value at runtime** is enabled.
+- Supports restrictions on file type and file size.
+
+Your shell script can then read the file directly from the mount path during execution.
+
+:::note
+The **File** type variable is available in **Execute custom task** in Pre-Build and Post-Build stages. It is also supported in user-created plugins — if you save a custom task that has a File input variable as a plugin, the File variable carries over and works in that plugin.
+:::
+
+## Prerequisites
+
+Before you begin, ensure the following:
+
+- You have an existing **Build Pipeline** configured for your application. Refer to [CI Pipeline](https://docs.devtron.ai/docs/user-guide/creating-application/workflow/ci-pipeline) to set one up.
+- You have **Admin**, **Manager**, or **Super Admin** permission on the application to configure the pipeline.
+
+## Step 1 — Add a File Variable to a Pre-Build Task
+
+1. Go to your application and navigate to **App Configuration** → **Workflow Editor**.
+2. Click on your CI pipeline to open the **Edit build pipeline** window.
+3. Select the **Pre-Build stage** tab (or **Post-Build stage**, depending on your use case).
+4. Click **+ Add task** and choose **Execute custom task**.
+5. Enter a **Task name** and optionally a **Description**.
+6. Under **Input variables**, click the **+** icon next to the **VARIABLE** column header to add a new variable row.
+7. Enter a variable name (e.g., `file`).
+8. In the **TYPE** dropdown, select **File**.
+
+
+
+:::info
+The **TYPE** dropdown includes: String, Number, Boolean, Date, and **File**.
+:::
+
+## Step 2 — Configure the File Variable
+
+When you select **File** as the variable type, a configuration panel opens with the following options:
+
+
+
+| Field | Required | Description |
+|---|---|---|
+| **File mount path** | Yes | The absolute path inside the build container where the uploaded file will be available. Default: `/devtroncd`. Your shell script references the file from this path. |
+| **Restrict file type** | No | Comma-separated list of allowed file extensions (e.g., `.env, .json, .tar`). Leave blank to allow all file types. |
+| **Restrict file size** | No | Maximum allowed file size in **KB** or **MB**. Leave blank for no size limit. |
+| **Ask value at runtime** | No | When checked along with marking the variable as **required**, the file upload becomes mandatory at build trigger time. The build is blocked until the user uploads a file. |
+
+:::tip
+Enable **Ask value at runtime** if the file is required for every build run. Without it, you can pre-upload a default file at pipeline configuration time — see [Using a Default File](#using-a-default-file-without-ask-value-at-runtime).
+:::
+
+## Step 3 — Write the Shell Script
+
+In the **Script** section of your task, reference the uploaded file using the mount path you configured in Step 2.
+
+:::note
+The file variable is scoped to the task it is defined in. If multiple tasks in the same stage need the same file, add the File variable to each task separately.
+:::
+
+**Example — Reading an uploaded `.env` file:**
+
+```bash
+#!/bin/sh
+set -eo pipefail
+
+# The uploaded file is available at the configured mount path
+CONFIG_FILE="/devtroncd/config.env"
+
+if [ -f "$CONFIG_FILE" ]; then
+ echo "Config file found. Loading environment variables..."
+ export $(cat "$CONFIG_FILE" | xargs)
+ echo "Build will proceed with DB_HOST=$DB_HOST"
+else
+ echo "Error: Config file not found at $CONFIG_FILE"
+ exit 1
+fi
+```
+
+:::note
+The filename inside the mount path will match the name of the file uploaded by the user at trigger time.
+:::
+
+Once done, click **Create Pipeline** (or **Update Pipeline** for an existing pipeline) to save. The file variable configuration will be enforced on the next build trigger.
+
+## Step 4 — Trigger a Build and Upload the File
+
+When you trigger a build for this pipeline, Devtron enforces the file upload if **Ask value at runtime** is enabled.
+
+1. Navigate to **Build and Deploy** and click **Select Material** on your pipeline.
+2. In the **Build Pipeline** modal, go to the **Code Source** tab and select the branch and commit you want to build.
+3. Click **Start Build**.
+
+ If the file variable has **Ask value at runtime** enabled and no file has been uploaded, Devtron blocks the build and displays an error: **"Please resolve all the errors before starting the build"**. The **Parameters** tab will be highlighted with a red indicator.
+
+ 
+
+4. Click the **Parameters** tab. The **Runtime parameters** table lists your file variable with a `*` asterisk indicating it is required, and the **Value** field outlined in red showing **Upload file...**.
+
+ 
+
+5. Click **Upload file...** and select the file from your local machine.
+6. Once uploaded, the red indicator clears. Click **Start Build** to proceed.
+
+
+
+## Using a Default File (Without Ask Value at Runtime)
+
+If your pipeline uses the same file for most builds and only needs occasional overrides, you can pre-upload a default file directly in the pipeline editor — without enabling **Ask value at runtime**.
+
+1. Follow Steps 1–2 above to configure the File variable.
+2. Leave **Ask value at runtime** unchecked.
+3. In the **Value** field of the variable, click **Upload file...** and select a default file from your local machine.
+4. Save the pipeline.
+
+This default file will be used automatically for every build run. Users can still override it at trigger time by uploading a different file in the **Parameters** tab — but the build will not be blocked if they don't.
+
+:::note
+If **Ask value at runtime** is not enabled and no default file is uploaded, the variable will be empty at build time. Ensure your script handles this gracefully.
+:::
+
+## How the File Is Available Inside the Build Container
+
+Once the build starts, the file is mounted at the path you configured (e.g., `/devtroncd`). Your script can access it directly:
+
+```bash
+# List files at the mount path to confirm the upload
+ls /devtroncd/
+
+# Reference the file in your script
+cat /devtroncd/config.env
+```
+
+:::note
+The uploaded file is available **only for the duration of the build**. It is not persisted after the build container terminates. Do not rely on this file being available in subsequent builds or other pipeline stages. For sensitive files such as certificates or secrets, the file is discarded once the build completes, leaving no residual copy in the system.
+:::
+
+## Use Cases
+
+| Use Case | Recommended File Type |
+|---|---|
+| Inject environment-specific variables without committing to Git | `.env` |
+| Provide SSL/TLS certificates required during the build | `.pem`, `.crt` |
+| Pass a license key file needed by a build tool | `.lic`, `.key` |
+| Upload an environment-specific configuration file | `.json`, `.yaml` |
+| Provide a secrets archive for deployment tooling | `.tar`, `.zip` |
+
+## Notes
+
+- File variables are supported in both **Pre-Build** and **Post-Build** stages, inside **Execute custom task** only.
+- The file variable is **scoped to the task** it is defined in. Add it to each task separately if multiple tasks need the same file.
+- The file upload is **per-build** — if **Ask value at runtime** is enabled, a fresh upload is required for each build trigger.
+- If **Ask value at runtime** is not enabled, you can pre-upload a default file directly in the pipeline editor. This file will be used for every build run unless overridden at trigger time.
+- The mount path `/devtroncd` is writable inside the build container and is the recommended default.
+- Uploaded files are **ephemeral** — they exist only for the duration of the build and are not retained afterward.
+
+## Troubleshooting
+
+| Issue | Possible Cause | Resolution |
+|---|---|---|
+| Build starts without prompting for a file | **Ask value at runtime** is not checked | Edit the pipeline and enable **Ask value at runtime** on the file variable |
+| Script cannot find the file at the mount path | Wrong mount path configured, or filename mismatch | Confirm the mount path in the variable config and check the exact filename with `ls /devtroncd/` |
+| File upload field shows no error but build fails | File type or size restriction violated | Check the **Restrict file type** and **Restrict file size** settings in the variable config |
+| Parameters tab does not show the file variable | Variable was not saved correctly | Re-open the pipeline editor and verify the variable exists with type **File** |
+| Next build uses the old default file | **Ask value at runtime** is off and no new file was uploaded | Upload a new file in the Parameters tab at trigger time, or update the default file in the pipeline editor |
+| File is not available in a subsequent pipeline stage | Files are ephemeral and scoped to the build container | Re-upload the file for each build, or store the file in an artifact or external storage between stages |
+
+## Related Topics
+
+- [Workflow Editor](https://docs.devtron.ai/docs/user-guide/creating-application/workflow)
+- [Pre-Build/Post-Build Stages](https://docs.devtron.ai/docs/user-guide/creating-application/workflow/pre-post-tasks)
+- [CI Pipeline](https://docs.devtron.ai/docs/user-guide/creating-application/workflow/ci-pipeline)
+- [Triggering CI](https://docs.devtron.ai/docs/user-guide/deploying-application/triggering-ci)
+- [Runtime Parameters](https://docs.devtron.ai/docs/user-guide/deploying-application/runtime-parameters)
\ No newline at end of file
diff --git a/docs/user-guide/creating-application/workflow/pre-post-tasks.md b/docs/user-guide/creating-application/workflow/pre-post-tasks.md
index 92ffe7af43..a11bb662fd 100755
--- a/docs/user-guide/creating-application/workflow/pre-post-tasks.md
+++ b/docs/user-guide/creating-application/workflow/pre-post-tasks.md
@@ -200,7 +200,7 @@ Let's take an example of a **Shell task** in the Pre-Build stage that ensures th
| `Task Name`| `check-db-name`| Required| Enter a name for the task|
| `Task Description`| `This task stops the build if the database name is not 'prod-db'` | Optional | Short description for the task|
| `Task Type` | `Shell`| Optional| Select the preferred task type |
-| `Input variables`| Refer the [Input Variable table](#input-variable-table) below | Optional|
These variables provide dynamic values to the script at the time of execution and are defined directly in the UI.
Variable name: Alphanumeric chars and (_) only
Source or input value: The variable's value can be global, output from the previous task, or a custom value. Accepted data types include: STRING
These variables provide dynamic values to the script at the time of execution and are defined directly in the UI.
Variable name: Alphanumeric chars and (_) only
Source or input value: The variable's value can be global, output from the previous task, or a custom value. Accepted data types include: STRING. To upload a file as an input variable, see [File Upload During Build Time](./file-upload-during-build.md).
|
| `Trigger/Skip condition` | Not required for this example | Optional| A conditional statement to execute or skip the task|
| `Script`| Refer the [Script](#script-1) below| Required| Custom script for executing tasks|
| `Output directory path` | Not required for this example | Optional| Directory path where output files such as logs, errors, etc. will be available after the execution.|
@@ -279,7 +279,7 @@ Since we have already configured a shell task to validate the database name, we
| `Task name`| `verify-db-connectivity`| Required|Enter a name for the task|
| `Description`| Verify DB connection before build | Optional| A descriptive message for the task|
| `Task type`| `Container Image`| Optional| Allows you to execute commands and scripts inside a custom Docker container|
-| `Input variables`| Refer the [Input Variable table](#input-variable-table-1) below | Optional|
These variables provide dynamic values to the script and are defined directly in the UI.
Variable name: Alphanumeric chars and (_) only
Source or input value: The variable's value can be global, output from the previous task, or a custom value. Accepted data types include: STRING
These variables provide dynamic values to the script and are defined directly in the UI.
Variable name: Alphanumeric chars and (_) only
Source or input value: The variable's value can be global, output from the previous task, or a custom value. Accepted data types include: STRING. To upload a file as an input variable, see [File Upload During Build Time](./file-upload-during-build.md).
|
| `Trigger/Skip condition`| `DB_VALIDATION == pass`| Optional| Execute or skip the task based on the condition provided.|
| `Container image`| `mysql:8.0`| Required| Select an image from the drop-down list or enter a custom value in the format `:`|
| `Mount custom code`| Refer below [Mount custom code](#mount-custom-code) section| Optional|
Enable to mount the custom code in the container. Enter the script in the box below.
**Mount above code at** (required): Path where the code should be mounted, eg, `/scripts`