---
title: New Placement Hints for Workers
description: Explicit placement hints for legacy cloud infrastructure.
image: https://developers.cloudflare.com/changelog-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://developers.cloudflare.com/changelog/) 

## New Placement Hints for Workers

Jan 22, 2026 

[ Workers ](https://developers.cloudflare.com/workers/) 

You can now configure Workers to run close to infrastructure in legacy cloud regions to minimize latency to existing services and databases. This is most useful when your Worker makes multiple round trips.

To [set a placement hint](https://developers.cloudflare.com/workers/configuration/placement/#configure-explicit-placement-hints), set the `placement.region` property in your Wrangler configuration file:

* [  wrangler.jsonc ](#tab-panel-2717)
* [  wrangler.toml ](#tab-panel-2718)

**JSONC**

```jsonc
{
  "placement": {
    "region": "aws:us-east-1",
  },
}
```

**TOML**

```toml
[placement]
region = "aws:us-east-1"
```

Placement hints support Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure region identifiers. Workers run in the [Cloudflare data center ↗](https://www.cloudflare.com/network/) with the lowest latency to the specified cloud region.

If your existing infrastructure is not in these cloud providers, expose it to placement probes with `placement.host` for layer 4 checks or `placement.hostname` for layer 7 checks. These probes are designed to locate single-homed infrastructure and are not suitable for anycasted or multicasted resources.

* [  wrangler.jsonc ](#tab-panel-2719)
* [  wrangler.toml ](#tab-panel-2720)

**JSONC**

```jsonc
{
  "placement": {
    "host": "my_database_host.com:5432",
  },
}
```

**TOML**

```toml
[placement]
host = "my_database_host.com:5432"
```

* [  wrangler.jsonc ](#tab-panel-2721)
* [  wrangler.toml ](#tab-panel-2722)

**JSONC**

```jsonc
{
  "placement": {
    "hostname": "my_api_server.com",
  },
}
```

**TOML**

```toml
[placement]
hostname = "my_api_server.com"
```

This is an extension of [Smart Placement](https://developers.cloudflare.com/workers/configuration/placement/#enable-smart-placement), which automatically places your Workers closer to back-end APIs based on measured latency. When you do not know the location of your back-end APIs or have multiple back-end APIs, set `mode: "smart"`:

* [  wrangler.jsonc ](#tab-panel-2723)
* [  wrangler.toml ](#tab-panel-2724)

**JSONC**

```jsonc
{
  "placement": {
    "mode": "smart",
  },
}
```

**TOML**

```toml
[placement]
mode = "smart"
```

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://developers.cloudflare.com/changelog/post/2026-01-22-explicit-placement-hints/#page","headline":"New Placement Hints for Workers · Changelog","description":"Explicit placement hints for legacy cloud infrastructure.","url":"https://developers.cloudflare.com/changelog/post/2026-01-22-explicit-placement-hints/","inLanguage":"en","image":"https://developers.cloudflare.com/changelog-preview.png","dateModified":"2026-01-22","datePublished":"2026-01-22","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}
```