diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx
index 9f34d3a860e2af2..c0e55b0ead6534b 100644
--- a/src/content/docs/workers/wrangler/commands.mdx
+++ b/src/content/docs/workers/wrangler/commands.mdx
@@ -44,16 +44,7 @@ Wrangler offers a number of commands to manage your Cloudflare Workers.
 
 :::note
 
-The following global flags work on every command, with some exceptions for `pages` commands.
-
-- `--help` <Type text="boolean" />
-  - Show help.
-- `--version` <Type text="boolean" />
-  - Show version number.
-- `--config` <Type text="string" /> (not supported by Pages)
-  - Path to `.toml` configuration file.
-- `--experimental-json-config` <Type text="boolean" /> (not supported by Pages)
-  - ⚠️ This is an experimental command. Read configuration from a `wrangler.json` file, instead of `wrangler.toml`. `wrangler.json` is a [JSONC](https://code.visualstudio.com/docs/languages/json#_json-with-comments) file.
+<Render file="wrangler-commands/global-flags" product="workers" />
 
 :::
 
@@ -137,6 +128,8 @@ wrangler docs [<COMMAND>]
 - `COMMAND` <Type text="string" /> <MetaInfo text="optional" />
   - The Wrangler command you want to learn more about. This opens your default browser to the section of the documentation that describes the command.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ## `init`
 
 :::note
@@ -159,6 +152,8 @@ wrangler init [<NAME>] [OPTIONS]
   - Fetch a Worker initialized from the dashboard. This is done by passing the flag and the Worker name. `wrangler init --from-dash <WORKER_NAME>`.
   - The `--from-dash` command will not automatically sync changes made to the dashboard after the command is used. Therefore, it is recommended that you continue using the CLI.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `generate`
@@ -180,6 +175,8 @@ wrangler generate [<NAME>] [TEMPLATE]
 - `TEMPLATE` <Type text="string" /> <MetaInfo text="optional" />
   - The URL of a GitHub template, with a default [worker-template](https://github.com/cloudflare/worker-template). Browse a list of available templates on the [cloudflare/workers-sdk](https://github.com/cloudflare/workers-sdk/tree/main/templates#usage) repository.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `d1`
@@ -200,6 +197,8 @@ wrangler d1 create <DATABASE_NAME> [OPTIONS]
   - Provide an optional [location hint](/d1/configuration/data-location/) for your database leader.
   - Available options include `weur` (Western Europe), `eeur` (Eastern Europe), `apac` (Asia Pacific), `oc` (Oceania), `wnam` (Western North America), and `enam` (Eastern North America).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `info`
 
 Get information about a D1 database, including the current database size and state.
@@ -213,6 +212,8 @@ wrangler d1 info <DATABASE_NAME> [OPTIONS]
 - `--json` <Type text="boolean" /> <MetaInfo text="optional" />
   - Return output as JSON rather than a table.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list`
 
 List all D1 databases in your account.
@@ -224,6 +225,8 @@ wrangler d1 list [OPTIONS]
 - `--json` <Type text="boolean" /> <MetaInfo text="optional" />
   - Return output as JSON rather than a table.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete a D1 database.
@@ -237,6 +240,8 @@ wrangler d1 delete <DATABASE_NAME> [OPTIONS]
 - `-y, --skip-confirmation` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip deletion confirmation prompt.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `execute`
 
 Execute a query on a D1 database.
@@ -272,6 +277,8 @@ You must provide either `--command` or `--file` for this command to run successf
 - `--batch-size` <Type text="number" /> <MetaInfo text="optional" />
   - Number of queries to send in a single batch.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `export`
 
 Export a D1 database or table's schema and/or content to a `.sql` file.
@@ -293,6 +300,8 @@ wrangler d1 export <DATABASE_NAME> [OPTIONS]
 - `--no-schema` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
   - Controls whether export SQL file contains database schema. Note that `--no-schema=true` is not recommended due to a known wrangler limitation that intreprets the value as false.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `time-travel restore`
 
 Restore a database to a specific point-in-time using [Time Travel](/d1/reference/time-travel/).
@@ -310,6 +319,8 @@ wrangler d1 time-travel restore <DATABASE_NAME> [OPTIONS]
 - `--json` <Type text="boolean" /> <MetaInfo text="optional" />
   - Return output as JSON rather than a table.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `time-travel info`
 
 Inspect the current state of a database for a specific point-in-time using [Time Travel](/d1/reference/time-travel/).
@@ -325,6 +336,8 @@ wrangler d1 time-travel info <DATABASE_NAME> [OPTIONS]
 - `--json` b<Type text="boolean" /> <MetaInfo text="optional" />
   - Return output as JSON rather than a table.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `backup create`
 
 :::caution
@@ -343,6 +356,8 @@ wrangler d1 backup create <DATABASE_NAME>
 - `DATABASE_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the D1 database to backup.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `backup list`
 
 :::caution
@@ -361,6 +376,8 @@ wrangler d1 backup list <DATABASE_NAME>
 - `DATABASE_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the D1 database to list the backups of.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `backup restore`
 
 :::caution
@@ -381,6 +398,8 @@ wrangler d1 backup restore <DATABASE_NAME> <BACKUP_ID>
 - `BACKUP_ID` <Type text="string" /> <MetaInfo text="required" />
   - The ID of the backup you wish to restore.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `backup download`
 
 :::caution
@@ -403,6 +422,8 @@ wrangler d1 backup download <DATABASE_NAME> <BACKUP_ID>
 - `--output` <Type text="string" /> <MetaInfo text="optional" />
   - The `.sqlite3` file to write to (defaults to `'<DB_NAME>.<SHORT_BACKUP_ID>.sqlite3'`).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `migrations create`
 
 Create a new migration.
@@ -422,6 +443,8 @@ wrangler d1 migrations create <DATABASE_NAME> <MIGRATION_NAME>
 - `MIGRATION_NAME` <Type text="string" /> <MetaInfo text="required" />
   - A descriptive name for the migration you wish to create.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `migrations list`
 
 View a list of unapplied migration files.
@@ -441,6 +464,8 @@ wrangler d1 migrations list <DATABASE_NAME> [OPTIONS]
 - `--preview` <Type text="boolean" /> <MetaInfo text="optional" />
   - Show the list of unapplied migration files on your preview D1 database (as defined by `preview_database_id` in [`wrangler.toml`](/workers/wrangler/configuration/#d1-databases)).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `migrations apply`
 
 Apply any unapplied migrations.
@@ -472,6 +497,8 @@ wrangler d1 migrations apply <DATABASE_NAME> [OPTIONS]
 - `--batch-size` <Type text="number" /> <MetaInfo text="optional" />
   - Number of queries to send in a single batch.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `hyperdrive`
@@ -505,6 +532,8 @@ npx wrangler vectorize create <INDEX_NAME> [--dimensions=<NUM_DIMENSIONS>] [--me
 - `--deprecated-v1` <Type text="boolean" /> <MetaInfo text="optional" />
   - Create a legacy Vectorize index. Please note that legacy Vectorize indexes are on a [deprecation path](/vectorize/reference/transition-vectorize-legacy).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list`
 
 List all Vectorize indexes in your account, including the configured dimensions and distance metric.
@@ -516,6 +545,8 @@ npx wrangler vectorize list
 - `--deprecated-v1` <Type text="boolean" /> <MetaInfo text="optional" />
   - List legacy Vectorize indexes. Please note that legacy Vectorize indexes are on a [deprecation path](/vectorize/reference/transition-vectorize-legacy).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `get`
 
 Get details about an individual index, including its configuration.
@@ -529,6 +560,8 @@ npx wrangler vectorize get <INDEX_NAME>
 - `--deprecated-v1` <Type text="boolean" /> <MetaInfo text="optional" />
   - Get a legacy Vectorize index. Please note that legacy Vectorize indexes are on a [deprecation path](/vectorize/reference/transition-vectorize-legacy).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `info`
 
 Get some additional information about an individual index, including the vector count and details about the last processed mutation.
@@ -540,6 +573,8 @@ npx wrangler vectorize info <INDEX_NAME>
 - `INDEX_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the index to fetch details for.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete a Vectorize index.
@@ -555,6 +590,8 @@ npx wrangler vectorize delete <INDEX_NAME> [OPTIONS]
 - `--deprecated-v1` <Type text="boolean" /> <MetaInfo text="optional" />
   - Delete a legacy Vectorize index. Please note that legacy Vectorize indexes are on a [deprecation path](/vectorize/reference/transition-vectorize-legacy).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `insert`
 
 Insert vectors into an index.
@@ -572,6 +609,8 @@ npx wrangler vectorize insert <INDEX_NAME> [OPTIONS]
 - `--deprecated-v1` <Type text="boolean" /> <MetaInfo text="optional" />
   - Insert into a legacy Vectorize index. Please note that legacy Vectorize indexes are on a [deprecation path](/vectorize/reference/transition-vectorize-legacy).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `upsert`
 
 Upsert vectors into an index. Existing vectors in the index would be overwritten.
@@ -587,6 +626,8 @@ npx wrangler vectorize upsert <INDEX_NAME> [OPTIONS]
 - `--batch-size` <Type text="number" /> <MetaInfo text="optional" />
   - The number of vectors to insert at a time (default: `5000`).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `query`
 
 Query a Vectorize index for similar vectors.
@@ -612,6 +653,8 @@ npx wrangler vectorize query <INDEX_NAME> [OPTIONS]
 - `--filter` <Type text="string" /> <MetaInfo text="optional" />
   - Filter vectors based on this metadata filter. Example: `'{ 'p1': 'abc', 'p2': { '$ne': true }, 'p3': 10, 'p4': false, 'nested.p5': 'abcd' }'`
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `get-vectors`
 
 Fetch vectors from a Vectorize index using the provided ids.
@@ -625,6 +668,8 @@ npx wrangler vectorize get-vectors <INDEX_NAME> [OPTIONS]
 - `--ids` <Type text="array" /> <MetaInfo text="required" />
   - List of ids for which vectors must be fetched.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete-vectors`
 
 Delete vectors in a Vectorize index using the provided ids.
@@ -638,6 +683,8 @@ npx wrangler vectorize delete-vectors <INDEX_NAME> [OPTIONS]
 - `--ids` <Type text="array" /> <MetaInfo text="required" />
   - List of ids corresponding to the vectors that must be deleted.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `create-metadata-index`
 
 Enable metadata filtering on the specified property.
@@ -653,6 +700,8 @@ npx wrangler vectorize create-metadata-index <INDEX_NAME> [OPTIONS]
 - `--type` <Type text="string" /> <MetaInfo text="required" />
   - Data type of the property. Must be one of `string`, `number`, or `boolean`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list-metadata-index`
 
 List metadata properties on which metadata filtering is enabled.
@@ -664,6 +713,8 @@ npx wrangler vectorize list-metadata-index <INDEX_NAME> [OPTIONS]
 - `INDEX_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the Vectorize index for which metadata indexes needs to be fetched.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete-metadata-index`
 
 Disable metadata filtering on the specified property.
@@ -677,6 +728,8 @@ npx wrangler vectorize delete-metadata-index <INDEX_NAME> [OPTIONS]
 - `--property-name` <Type text="string" /> <MetaInfo text="required" />
   - Metadata property for which metadata filtering should be disabled.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `dev`
@@ -774,6 +827,8 @@ As of Wrangler v3.2.0, `wrangler dev` is supported by any Linux distributions pr
 - `--alias` `Array<string>`
   - Specify modules to alias using [module aliasing](/workers/wrangler/configuration/#module-aliasing).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 `wrangler dev` is a way to [locally test](/workers/testing/local-development/) your Worker while developing. With `wrangler dev` running, send HTTP requests to `localhost:8787` and your Worker should execute as expected. You will also see `console.log` messages and exceptions appearing in your terminal.
 
 ---
@@ -848,6 +903,8 @@ None of the options for this command are required. Also, many can be set in your
 - `--dispatch-namespace` <Type text="string" /> <MetaInfo text="optional" />
   - Specify the [Workers for Platforms dispatch namespace](/cloudflare-for-platforms/workers-for-platforms/get-started/configuration/#2-create-a-dispatch-namespace) to upload this Worker to.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `publish`
@@ -883,6 +940,8 @@ wrangler delete [<SCRIPT>] [OPTIONS]
 - `--dry-run` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
   - Do not actually delete the Worker. This is useful for testing the output of `wrangler delete`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 <Render file="wrangler-commands/kv" product="workers" />
 
 ---
@@ -913,6 +972,8 @@ wrangler r2 bucket create <NAME>
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the R2 bucket is created. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `info`
 
 Get information about an R2 bucket, including the bucket size and number of objects.
@@ -926,6 +987,8 @@ wrangler r2 bucket info <NAME>
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete an R2 bucket.
@@ -937,6 +1000,8 @@ wrangler r2 bucket delete <NAME>
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the R2 bucket to delete.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list`
 
 List R2 bucket in the current account.
@@ -945,6 +1010,8 @@ List R2 bucket in the current account.
 wrangler r2 bucket list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `dev-url enable`
 
 Enable public access via the [r2.dev URL](/r2/buckets/public-buckets/#enable-managed-public-access) for an R2 bucket.
@@ -960,6 +1027,8 @@ wrangler r2 bucket dev-url enable <NAME> [OPTIONS]
 - `--force` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip confirmation when enabling public access via r2.dev URL.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `dev-url disable`
 
 Disable public access via the [r2.dev URL](/r2/buckets/public-buckets/#enable-managed-public-access) for an R2 bucket.
@@ -975,6 +1044,8 @@ wrangler r2 bucket dev-url disable <NAME> [OPTIONS]
 - `--force` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip confirmation when disabling public access via r2.dev URL.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `dev-url get`
 
 Get the [r2.dev URL](/r2/buckets/public-buckets/#enable-managed-public-access) and status for an R2 bucket.
@@ -988,6 +1059,8 @@ wrangler r2 bucket dev-url get <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `domain add`
 
 Connect a [custom domain](/r2/buckets/public-buckets/#custom-domains) to an R2 bucket.
@@ -1009,6 +1082,8 @@ wrangler r2 bucket domain add <NAME> [OPTIONS]
 - `--force` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip confirmation when adding the custom domain.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `domain remove`
 
 Remove a [custom domain](/r2/buckets/public-buckets/#custom-domains) from an R2 bucket.
@@ -1026,6 +1101,8 @@ wrangler r2 bucket domain remove <NAME> [OPTIONS]
 - `--force` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip confirmation when removing the custom domain.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `domain update`
 
 Update settings for a [custom domain](/r2/buckets/public-buckets/#custom-domains) connected to an R2 bucket.
@@ -1043,6 +1120,8 @@ wrangler r2 bucket domain update <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `domain list`
 
 List [custom domains](/r2/buckets/public-buckets/#custom-domains) for an R2 bucket.
@@ -1056,6 +1135,8 @@ wrangler r2 bucket domain list <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `notification create`
 
 Create an [event notification](/r2/buckets/event-notifications/) rule for an R2 bucket.
@@ -1077,6 +1158,8 @@ wrangler r2 bucket notification create <NAME> [OPTIONS]
 - `--description` <Type text="string" /> <MetaInfo text="optional" />
   - A description that can be used to identify the event notification rule after creation.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `notification delete`
 
 Remove an event notification rule from a bucket's [event notification](/r2/buckets/event-notifications/) configuration.
@@ -1092,6 +1175,8 @@ wrangler r2 bucket notification delete <NAME> [OPTIONS]
 - `--rule` <Type text="string" /> <MetaInfo text="optional" />
   - The ID of the event notification rule to delete.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `notification list`
 
 List the [event notification](/r2/buckets/event-notifications/) rules for a bucket.
@@ -1103,6 +1188,8 @@ wrangler r2 bucket notification list <NAME>
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the R2 bucket to get event notification rules for.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `lifecycle add`
 
 Add an [object lifecycle](/r2/buckets/object-lifecycles/) rule to an R2 bucket.
@@ -1132,6 +1219,8 @@ wrangler r2 bucket lifecycle add <NAME> [OPTIONS]
 - `--force` <Type text="boolean" /> <MetaInfo text="optional" />
   - Skip confirmation when adding the lifecycle rule.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `lifecycle remove`
 
 Remove an [object lifecycle](/r2/buckets/object-lifecycles/) rule from an R2 bucket.
@@ -1147,6 +1236,8 @@ wrangler r2 bucket lifecycle remove <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `lifecycle list`
 
 List [object lifecycle](/r2/buckets/object-lifecycles/) rules for an R2 bucket.
@@ -1160,6 +1251,8 @@ wrangler r2 bucket lifecycle list <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `lifecycle set`
 
 Set the [object lifecycle](/r2/buckets/object-lifecycles/) configuration for an R2 bucket from a JSON file.
@@ -1175,6 +1268,8 @@ wrangler r2 bucket lifecycle set <NAME> [OPTIONS]
 - `--jurisdiction` <Type text="string" /> <MetaInfo text="optional" />
   - The jurisdiction where the bucket exists, if a jurisdiction has been specified. Refer to [jurisdictional restrictions](/r2/reference/data-location/#jurisdictional-restrictions).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `sippy enable`
 
 Enable [Sippy](/r2/data-migration/sippy/) incremental migration for a bucket.
@@ -1211,6 +1306,8 @@ wrangler r2 bucket sippy enable <NAME> [OPTIONS]
   - The private key for your Google Cloud service account key. Requires [read and list access](/r2/data-migration/sippy/#google-cloud-storage).
 - Note that you must provide either `service-account-key-file` or `client_email` and `private_key` for this command to run successfully.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `sippy disable`
 
 Disable [Sippy](/r2/data-migration/sippy/) incremental migration for a bucket.
@@ -1222,6 +1319,8 @@ wrangler r2 bucket sippy disable <NAME>
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the R2 bucket to disable Sippy.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `sippy get`
 
 Get the status of [Sippy](/r2/data-migration/sippy/) incremental migration for a bucket.
@@ -1233,12 +1332,16 @@ wrangler r2 bucket sippy get <NAME>
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of the R2 bucket to get the status of Sippy.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `r2 object`
 
 Interact with R2 objects.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 The `r2 object` commands allow you to manage application data in the Cloudflare network to be accessed from Workers using [the R2 API](/r2/api/workers/workers-api-reference/).
@@ -1259,6 +1362,8 @@ wrangler r2 object get <OBJECT_PATH> [OPTIONS]
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `put`
 
 Create an object in an R2 bucket.
@@ -1290,6 +1395,8 @@ wrangler r2 object put <OBJECT_PATH> [OPTIONS]
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete an object in an R2 bucket.
@@ -1305,6 +1412,8 @@ wrangler r2 object delete <OBJECT_PATH> [OPTIONS]
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `secret`
@@ -1322,16 +1431,14 @@ wrangler secret put <KEY> [OPTIONS]
 ```
 
 - `KEY` <Type text="string" /> <MetaInfo text="required" />
-
   - The variable name for this secret to be accessed in the Worker.
-
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
-
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
-
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 When running this command, you will be prompted to input the secret's value:
 
 ```sh
@@ -1359,16 +1466,14 @@ wrangler secret delete <KEY> [OPTIONS]
 ```
 
 - `KEY` <Type text="string" /> <MetaInfo text="required" />
-
   - The variable name for this secret to be accessed in the Worker.
-
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
-
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
-
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list`
 
 List the names of all the secrets for a Worker.
@@ -1378,13 +1483,12 @@ wrangler secret list [OPTIONS]
 ```
 
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
-
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
-
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
-
   - Perform on a specific environment
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of listing the secrets for the current Worker.
 
 ```sh
@@ -1411,17 +1515,15 @@ wrangler secret:bulk [<FILENAME>] [OPTIONS]
 ```
 
 - `FILENAME` <Type text="string" /> <MetaInfo text="optional" />
-
   - The JSON file containing key-value pairs to upload as secrets, in the form `{"SECRET_NAME": "secret value", ...}`.
   - If omitted, Wrangler expects to receive input from `stdin` rather than a file.
-
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
-
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
-
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of uploading secrets from a JSON file redirected to `stdin`. When complete, the output summary will show the number of secrets uploaded and the number of secrets that failed to upload.
 
 ```json
@@ -1470,6 +1572,8 @@ wrangler workflows list
 - `--per-page` <Type text="number" /> <MetaInfo text="optional" />
   - Configure the maximum number of Workflows to show per page.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `instances`
 
 Manage and interact with specific instances of a Workflow.
@@ -1485,6 +1589,8 @@ wrangler workflows instances list <WORKFLOW_NAME> [OPTIONS]
 - `WORKFLOW_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of a registered Workflow.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `instances describe`
 
 Describe a specific instance of a Workflow, including its current status, any persisted state, and per-step outputs.
@@ -1498,10 +1604,13 @@ wrangler workflows instances describe <WORKFLOW_NAME> <ID> [OPTIONS]
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The ID of a Workflow instance. You can optionally provide `latest` to refer to the most recently created instance of a Workflow.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ```sh
 # Passing `latest` instead of an explicit ID will describe the most recently queued instance
 wrangler workflows instances describe my-workflow latest
 ```
+
 ```sh output
 Workflow Name:         my-workflow
 Instance Id:           51c73fc8-7fd5-47d9-bd82-9e301506ee72
@@ -1529,6 +1638,8 @@ wrangler workflows instances terminate <WORKFLOW_NAME> <ID> [OPTIONS]
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The ID of a Workflow instance.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `instances pause`
 
 Pause (until resumed) a Workflow instance.
@@ -1542,6 +1653,8 @@ wrangler workflows instances pause <WORKFLOW_NAME> <ID> [OPTIONS]
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The ID of a Workflow instance.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `instances resume`
 
 Resume a paused Workflow instance.
@@ -1555,6 +1668,8 @@ wrangler workflows instances resume <WORKFLOW_NAME> <ID> [OPTIONS]
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The ID of a Workflow instance.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `describe`
 
 ```sh
@@ -1564,9 +1679,12 @@ wrangler workflows describe <WORKFLOW_NAME> [OPTIONS]
 - `WORKFLOW_NAME` <Type text="string" /> <MetaInfo text="required" />
   - The name of a registered Workflow.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `trigger`
 
 Trigger (create) a Workflow instance.
+
 ```sh
 wrangler workflows trigger <WORKFLOW_NAME> <PARAMS> [OPTIONS]
 ```
@@ -1576,10 +1694,12 @@ wrangler workflows trigger <WORKFLOW_NAME> <PARAMS> [OPTIONS]
 - `PARAMS` <Type text="string" /> <MetaInfo text="optional" />
   - The parameters to pass to the Workflow as an event. Must be a JSON-encoded string.
 
- ```sh
- # Pass optional params to the Workflow.
- wrangler workflows trigger my-workflow '{"hello":"world"}'
- ```
+<Render file="wrangler-commands/global-flags" product="workers" />
+
+```sh
+# Pass optional params to the Workflow.
+wrangler workflows trigger my-workflow '{"hello":"world"}'
+```
 
 {/*
 
@@ -1623,6 +1743,8 @@ wrangler tail <WORKER> [OPTIONS]
 - `--version-id` <Type text="string" /> <MetaInfo text="optional" />
   - Filter by Worker version.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 After starting `wrangler tail`, you will receive a live feed of console and exception logs for each request your Worker receives.
 
 If your Worker has a high volume of traffic, the tail might enter sampling mode. This will cause some of your messages to be dropped and a warning to appear in your tail logs. To prevent messages from being dropped, add the options listed above to filter the volume of tail messages.
@@ -1679,6 +1801,8 @@ wrangler pages dev [<DIRECTORY>] [OPTIONS]
 - `--https-cert-path` <Type text="string" /> <MetaInfo text="optional" />
   - Path to a custom certificate.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `download config`
 
 Download your Pages project config as a wrangler.toml file.
@@ -1687,6 +1811,8 @@ Download your Pages project config as a wrangler.toml file.
 wrangler pages download config <PROJECT_NAME>
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `project list`
 
 List your Pages projects.
@@ -1695,6 +1821,8 @@ List your Pages projects.
 wrangler pages project list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `project create`
 
 Create a new Cloudflare Pages project.
@@ -1708,6 +1836,8 @@ wrangler pages project create <PROJECT_NAME> [OPTIONS]
 - `--production-branch` <Type text="string" /> <MetaInfo text="optional" />
   - The name of the production branch of your project.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `project delete`
 
 Delete a Cloudflare Pages project.
@@ -1721,6 +1851,8 @@ wrangler pages project delete <PROJECT_NAME> [OPTIONS]
 - `--yes` <Type text="boolean" /> <MetaInfo text="optional" />
   - Answer `"yes"` to confirmation prompt.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `deployment list`
 
 List deployments in your Cloudflare Pages project.
@@ -1732,7 +1864,9 @@ wrangler pages deployment list [--project-name <PROJECT_NAME>]
 - `--project-name` <Type text="string" /> <MetaInfo text="optional" />
   - The name of the project you would like to list deployments for.
 - `--environment` <Type text="'production'|'preview'" /> <MetaInfo text="optional" />
-	- Environment type to list deployments for.
+  - Environment type to list deployments for.
+
+<Render file="wrangler-commands/global-flags" product="workers" />
 
 ### `deployment tail`
 
@@ -1763,6 +1897,8 @@ wrangler pages deployment tail [<DEPLOYMENT>] [OPTIONS]
 - `--ip` <Type text="(string|'self')\[]" /> <MetaInfo text="optional" />
   - Filter by the IP address the request originates from. Use `"self"` to show only messages from your own IP.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 Filtering with `--ip self` will allow tailing your deployed Functions beyond the normal request per second limits.
@@ -1791,6 +1927,8 @@ wrangler pages deploy <BUILD_OUTPUT_DIRECTORY> [OPTIONS]
 - `--commit-dirty` <Type text="boolean" /> <MetaInfo text="optional" />
   - Whether or not the workspace should be considered dirty for this deployment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 Your site is deployed to `<PROJECT_NAME>.pages.dev`. If you do not provide the `--project-name` argument, you will be prompted to enter a project name in your terminal after you run the command.
@@ -1805,6 +1943,8 @@ Publish a directory of static assets as a Pages deployment.
 wrangler pages publish [<DIRECTORY>] [OPTIONS]
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 This command has been deprecated as of v3 in favor of [`wrangler pages deploy`](#deploy-1). It will be removed in v4.
@@ -1820,13 +1960,12 @@ wrangler pages secret put <KEY> [OPTIONS]
 ```
 
 - `KEY` <Type text="string" /> <MetaInfo text="required" />
-
   - The variable name for this secret to be accessed in the Pages project.
-
 - `--project-name` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of your Pages project.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret delete`
 
 Delete a secret from a Pages project.
@@ -1836,13 +1975,12 @@ wrangler pages secret delete <KEY> [OPTIONS]
 ```
 
 - `KEY` <Type text="string" /> <MetaInfo text="required" />
-
   - The variable name for this secret to be accessed in the Pages project.
-
 - `--project-name` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of your Pages project.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret list`
 
 List the names of all the secrets for a Pages project.
@@ -1852,9 +1990,10 @@ wrangler pages secret list [OPTIONS]
 ```
 
 - `--project-name` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of your Pages project.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret bulk`
 
 Upload multiple secrets for a Pages project at once.
@@ -1864,14 +2003,13 @@ wrangler pages secret bulk [<FILENAME>] [OPTIONS]
 ```
 
 - `FILENAME` <Type text="string" /> <MetaInfo text="optional" />
-
   - The JSON file containing key-value pairs to upload as secrets, in the form `{"SECRET_NAME": "secret value", ...}`.
   - If omitted, Wrangler expects to receive input from `stdin` rather than a file.
-
 - `--project-name` <Type text="string" /> <MetaInfo text="optional" />
-
   - The name of your Pages project.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `queues`
@@ -1891,6 +2029,8 @@ wrangler queues create <name> [OPTIONS]
 - `--delivery-delay-secs` <Type text="number" /> <MetaInfo text="optional" />
   - How long a published message should be delayed for, in seconds. Must be a positive integer.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete an existing queue.
@@ -1902,6 +2042,8 @@ wrangler queues delete <name> [OPTIONS]
 - `name` <Type text="string" /> <MetaInfo text="required" />
   - The name of the queue to delete.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `list`
 
 List all queues in the current account.
@@ -1910,6 +2052,8 @@ List all queues in the current account.
 wrangler queues list [OPTIONS]
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `consumer`
 
 Manage queue consumer configurations.
@@ -1937,6 +2081,8 @@ wrangler queues consumer add <queue-name> <script-name> [OPTIONS]
 - `--retry-delay-secs` <Type text="number" /> <MetaInfo text="optional" />
   - How long a retried message should be delayed for, in seconds. Must be a positive integer.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `consumer remove`
 
 Remove a consumer from a queue.
@@ -1950,6 +2096,8 @@ wrangler queues consumer remove <queue-name> <script-name>
 - `script-name` <Type text="string" /> <MetaInfo text="required" />
   - The name of the Workers script to remove as the consumer.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `login`
@@ -1968,6 +2116,8 @@ wrangler login [OPTIONS]
   - Allows to choose your set of OAuth scopes. The set of scopes must be entered in a whitespace-separated list,
     for example, `npx wrangler login --scopes account:read user:read`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 `wrangler login` uses all the available scopes by default if no flags are provided.
@@ -2010,6 +2160,8 @@ Remove Wrangler's authorization for accessing your account. This command will in
 wrangler logout
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 If you are using `CLOUDFLARE_API_TOKEN` instead of OAuth, and you can logout by deleting your API token in the Cloudflare dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
@@ -2027,6 +2179,8 @@ Retrieve your user information and test your authentication configuration.
 wrangler whoami
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `versions`
@@ -2050,6 +2204,8 @@ wrangler versions upload [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `deploy`
 
 Deploy a previously created [version](/workers/configuration/versions-and-deployments/#versions) of your Worker all at once or create a [gradual deployment](/workers/configuration/versions-and-deployments/gradual-deployments/) to incrementally shift traffic to a new version by following an interactive prompt.
@@ -2061,6 +2217,8 @@ wrangler versions deploy [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 :::note
 
 The non-interactive version of this prompt is: `wrangler versions deploy version-id-1@percentage-1% version-id-2@percentage-2 -y`
@@ -2081,6 +2239,8 @@ wrangler versions list [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret put`
 
 Create or replace a secret for a Worker. Creates a new [version](/workers/configuration/versions-and-deployments/#versions) with modified secrets without [deploying](/workers/configuration/versions-and-deployments/#deployments) the Worker.
@@ -2096,6 +2256,8 @@ wrangler versions secret put <KEY> [OPTIONS]
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret delete`
 
 Delete a secret for a Worker. Creates a new [version](/workers/configuration/versions-and-deployments/#versions) with modified secrets without [deploying](/workers/configuration/versions-and-deployments/#deployments) the Worker.
@@ -2111,6 +2273,8 @@ wrangler versions delete <KEY> [OPTIONS]
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `secret bulk`
 
 Upload multiple secrets for a Worker at once. Creates a new [version](/workers/configuration/versions-and-deployments/#versions) with modified secrets without [deploying](/workers/configuration/versions-and-deployments/#deployments) the Worker.
@@ -2127,6 +2291,8 @@ wrangler versions secret bulk <FILENAME> [OPTIONS]
 - `--env` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific environment.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `triggers`
@@ -2146,6 +2312,8 @@ wrangler triggers deploy [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `deployments`
@@ -2167,6 +2335,8 @@ wrangler deployments list [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `status`
 
 Retrieve details for the most recent deployment. Details include `Created on`, `Author`, `Source`, an optional `Message`, and metadata about the `Version(s)` in the deployment.
@@ -2178,6 +2348,8 @@ wrangler deployments status
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - Perform on a specific Worker rather than inheriting from `wrangler.toml`.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ## `rollback`
 
 :::caution
@@ -2195,6 +2367,8 @@ wrangler rollback [<VERSION_ID>] [OPTIONS]
 - `--message` <Type text="string" /> <MetaInfo text="optional" />
   - Add message for rollback. Accepts empty string. When specified, interactive prompts for rollback confirmation and message are skipped.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## dispatch namespace
@@ -2207,6 +2381,8 @@ List all dispatch namespaces.
 wrangler dispatch-namespace list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `get`
 
 Get information about a dispatch namespace.
@@ -2216,9 +2392,10 @@ wrangler dispatch-namespace get <NAME>
 ```
 
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
-
   - The name of the dispatch namespace to get details about.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `create`
 
 Create a dispatch namespace.
@@ -2228,9 +2405,10 @@ wrangler dispatch-namespace create <NAME>
 ```
 
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
-
   - The name of the dispatch namespace to create.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `delete`
 
 Delete a dispatch namespace.
@@ -2245,9 +2423,10 @@ You must delete all user Workers in the dispatch namespace before it can be dele
 :::
 
 - `NAME` <Type text="string" /> <MetaInfo text="required" />
-
   - The name of the dispatch namespace to delete.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ### `rename`
 
 Rename a dispatch namespace.
@@ -2257,13 +2436,12 @@ wrangler dispatch-namespace get <OLD_NAME> <NEW_NAME>
 ```
 
 - `OLD_NAME` <Type text="string" /> <MetaInfo text="required" />
-
   - The previous name of the dispatch namespace.
-
 - `NEW_NAME` <Type text="string" /> <MetaInfo text="required" />
-
   - The new name of the dispatch namespace.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 ---
 
 ## `mtls-certificate`
@@ -2287,6 +2465,8 @@ wrangler mtls-certificate upload --cert <PATH> --key <PATH> [OPTIONS]
 - `--name` <Type text="string" /> <MetaInfo text="optional" />
   - The name assigned to the mTLS certificate at upload.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of using the `upload` command to upload an mTLS certificate.
 
 ```sh
@@ -2319,6 +2499,8 @@ List mTLS certificates associated with the current account ID.
 wrangler mtls-certificate list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of using the `list` command to upload an mTLS certificate.
 
 ```sh
@@ -2351,6 +2533,8 @@ wrangler mtls-certificate delete {--id <ID|--name <NAME>}
 - `--name` <Type text="string" />
   - The name assigned to the mTLS certificate at upload.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of using the `delete` command to delete an mTLS certificate.
 
 ```sh
@@ -2389,17 +2573,15 @@ The minimum required Wrangler version to use this command is 3.66.0.
 :::
 
 - `PATH` <Type text="string" /> <MetaInfo text="(default: `./worker-configuration.d.ts`)" />
-
   - The path to where **the `Env` types** for your Worker will be written.
   - The path must have a `d.ts` extension.
-
 - `--env-interface` <Type text="string" /> <MetaInfo text="(default: `Env`)" />
-
   - The name of the interface to generate for the environment object.
   - Not valid if the Worker uses the Service Worker syntax.
-
 - `--experimental-include-runtime` <Type text="string" /> <MetaInfo text="optional (default: `./.wrangler/types/runtime.d.ts`)" />
   - The path to where the **runtime types** file will be written.
   - Leave the path blank to use the default option, e.g. `npx wrangler types --x-include-runtime`
   - A custom path must be relative to the project root, e.g. `./my-runtime-types.d.ts`
-  - A custom path must have a `d.ts` extension.
\ No newline at end of file
+  - A custom path must have a `d.ts` extension.
+
+<Render file="wrangler-commands/global-flags" product="workers" />
diff --git a/src/content/partials/workers/wrangler-commands/global-flags.mdx b/src/content/partials/workers/wrangler-commands/global-flags.mdx
new file mode 100644
index 000000000000000..f33a99d9117be4d
--- /dev/null
+++ b/src/content/partials/workers/wrangler-commands/global-flags.mdx
@@ -0,0 +1,16 @@
+---
+{}
+---
+
+import { Type } from "~/components";
+
+The following global flags work on every command:
+
+- `--help` <Type text="boolean" />
+  - Show help.
+- `--version` <Type text="boolean" />
+  - Show version number.
+- `--config` <Type text="string" /> (not supported by Pages)
+  - Path to `.toml` configuration file.
+- `--experimental-json-config` <Type text="boolean" /> (not supported by Pages)
+  - ⚠️ This is an experimental command. Read configuration from a `wrangler.json` file, instead of `wrangler.toml`. `wrangler.json` is a [JSONC](https://code.visualstudio.com/docs/languages/json#_json-with-comments) file.
diff --git a/src/content/partials/workers/wrangler-commands/hyperdrive.mdx b/src/content/partials/workers/wrangler-commands/hyperdrive.mdx
index eb1d158aa7c2ae1..17e16e5b73001ec 100644
--- a/src/content/partials/workers/wrangler-commands/hyperdrive.mdx
+++ b/src/content/partials/workers/wrangler-commands/hyperdrive.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { AnchorHeading, Type, MetaInfo } from "~/components";
+import { AnchorHeading, Type, MetaInfo, Render } from "~/components";
 
 <AnchorHeading title="`create`" slug="hyperdrive-create" depth={3} />
 
@@ -39,6 +39,8 @@ wrangler hyperdrive create <CONFIG_NAME> [OPTIONS]
 - `--swr` <Type text="number" /> <MetaInfo text="optional" />
   - Stale While Revalidate - Indicates the number of seconds cache may serve the response after it becomes stale, cannot be set when caching is disabled.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 <AnchorHeading title="`update`" slug="hyperdrive-update" depth={3} />
 
 Update an existing Hyperdrive configuration.
@@ -76,6 +78,8 @@ wrangler hyperdrive update <ID> [OPTIONS]
 - `--swr` <Type text="number" /> <MetaInfo text="optional" />
   - Stale While Revalidate - Indicates the number of seconds cache may serve the response after it becomes stale, cannot be set when caching is disabled.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 <AnchorHeading title="`list`" slug="hyperdrive-list" depth={3} />
 
 List all Hyperdrive configurations.
@@ -84,6 +88,8 @@ List all Hyperdrive configurations.
 wrangler hyperdrive list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 <AnchorHeading title="`delete`" slug="hyperdrive-delete" depth={3} />
 
 Delete an existing Hyperdrive configuration.
@@ -95,6 +101,8 @@ wrangler hyperdrive delete <ID>
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The name of the Hyperdrive configuration to delete.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 <AnchorHeading title="`get`" slug="hyperdrive-get" depth={3} />
 
 Get an existing Hyperdrive configuration.
@@ -105,3 +113,5 @@ wrangler hyperdrive get <ID>
 
 - `ID` <Type text="string" /> <MetaInfo text="required" />
   - The name of the Hyperdrive configuration to get.
+
+<Render file="wrangler-commands/global-flags" product="workers" />
diff --git a/src/content/partials/workers/wrangler-commands/kv.mdx b/src/content/partials/workers/wrangler-commands/kv.mdx
index eed653bfa41dd57..57c116f170f4ad9 100644
--- a/src/content/partials/workers/wrangler-commands/kv.mdx
+++ b/src/content/partials/workers/wrangler-commands/kv.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-import { AnchorHeading, Type, MetaInfo } from "~/components";
+import { AnchorHeading, Type, MetaInfo, Render } from "~/components";
 
 ## `kv namespace`
 
@@ -33,6 +33,8 @@ wrangler kv namespace create <NAMESPACE> [OPTIONS]
 - `--preview` <Type text="boolean" /> <MetaInfo text="optional" />
   - Interact with a preview namespace (the `preview_id` value).
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of using the `create` command to create a KV namespace called `MY_KV`.
 
 ```sh
@@ -71,6 +73,8 @@ List all KV namespaces associated with the current account ID.
 wrangler kv namespace list
 ```
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example that passes the Wrangler command through the `jq` command:
 
 ```sh
@@ -112,6 +116,8 @@ This command requires `--binding` or `--namespace-id`.
 - `--preview` <Type text="boolean" /> <MetaInfo text="optional" />
   - Interact with a preview namespace instead of production.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example of deleting a KV namespace called `MY_KV.`
 
 ```sh
@@ -191,6 +197,8 @@ This command requires a `--binding` or `--namespace-id` flag.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example that puts a key-value into the namespace with binding name of `MY_KV`.
 
 ```sh
@@ -259,6 +267,8 @@ This command requires `--binding` or `--namespace-id`.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 Below is an example that passes the Wrangler command through the `jq` command:
 
 ```sh
@@ -307,6 +317,8 @@ Exactly one of `--binding` or `--namespace-id` is required.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example that gets the value of the `"my-key"` key from the KV namespace with binding name `MY_KV`.
 
 ```sh
@@ -345,6 +357,8 @@ Exactly one of `--binding` or `--namespace-id` is required.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 The following is an example that deletes the key-value pair with key `"my-key"` from the KV namespace with binding name `MY_KV`.
 
 ```sh
@@ -397,6 +411,8 @@ This command requires `--binding` or `--namespace-id`.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 This command takes a JSON file as an argument with a list of key-value pairs to upload. An example of JSON input:
 
 ```json
@@ -479,6 +495,8 @@ This command requires `--binding` or `--namespace-id`.
 - `--persist-to` <Type text="string" /> <MetaInfo text="optional" />
   - Specify directory for locally persisted data.
 
+<Render file="wrangler-commands/global-flags" product="workers" />
+
 This command takes a JSON file as an argument containing an array of keys to delete.
 
 The following is an example of the JSON input: