Skip to content

workers: fix Smart Placement terminology #27872

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elithrar merged 1 commit into from
Feb 3, 2026
Merged

workers: fix Smart Placement terminology #27872

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions src/content/docs/workers/configuration/placement.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ The latency from multiple round trips between Sydney and Frankfurt adds up. By p

![A user located in Sydney, AU connecting to a Worker in Frankfurt, DE which then makes multiple round trips to a database also located in Frankfurt, DE. ](~/assets/images/workers/platform/workers-smart-placement-enabled.png)

## Use smart placement
## Enable Smart Placement

Smart Placement automatically analyzes your Worker's traffic patterns and places it in an optimal location. Use Smart Placement when:

Expand Down Expand Up @@ -138,7 +138,7 @@ The header value includes a placement type and an airport code indicating the da
The `cf-placement` header may be removed before Smart Placement exits beta.
:::

## Use placement hints
## Configure explicit Placement Hints

Placement Hints let you explicitly specify where your Worker runs. Use Placement Hints when:

Expand Down Expand Up @@ -222,19 +222,19 @@ For a full list of region codes, refer to [AWS regions](https://docs.aws.amazon.

## Placement Behavior

Workers Placement behaves in similar fashion when either Smart Placement or Placement hints are used. The following behavior applies to both.
Workers placement behaves in similar fashion when either Smart Placement or Placement Hints are used. The following behavior applies to both.

### Review limitations

The following limitations apply to both smart placement and placement hints:
The following limitations apply to both Smart Placement and Placement Hints:

- Smart Placement only affects the execution of [fetch event handlers](/workers/runtime-apis/handlers/fetch/). It does not affect [RPC methods](/workers/runtime-apis/rpc/) or [named entrypoints](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints).
- Workers without a fetch event handler are ignored by Smart Placement.
- Placement only affects the execution of [fetch event handlers](/workers/runtime-apis/handlers/fetch/). It does not affect [RPC methods](/workers/runtime-apis/rpc/) or [named entrypoints](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints).
- Workers without a fetch event handler are ignored by placement.
- [Static assets](/workers/static-assets/) are always served from the location nearest to the incoming request. If your code retrieves assets via the [static assets binding](/workers/static-assets/binding/), assets are served from the location where your Worker runs.

### `cf-placement` header

Cloudflare adds a `cf-placement` header to all requests when placement is enabled. Use this header to check whether a request was routed with Smart Placement and where the Worker processed the request.
Cloudflare adds a `cf-placement` header to all requests when placement is enabled. Use this header to check whether a request was routed with placement and where the Worker processed the request.

The header value includes a placement type and an airport code indicating the data center location:

Expand Down