diff --git a/src/routes/changelog/(entries)/2026-07-14.markdoc b/src/routes/changelog/(entries)/2026-07-14.markdoc
new file mode 100644
index 0000000000..d070e154f1
--- /dev/null
+++ b/src/routes/changelog/(entries)/2026-07-14.markdoc
@@ -0,0 +1,13 @@
+---
+layout: changelog
+title: Upgraded default build resources for Sites and Functions
+date: 2026-07-14
+---
+
+We have upgraded the default build specification for Appwrite Sites and Functions on Cloud. Every deployment build now runs with **2 CPU cores and 2GB of memory**, replacing the previous 0.5 CPU and 512MB default. Lower build specifications have been removed.
+
+The new default applies to all plans, including Free, and requires no configuration changes. Expect faster dependency installs, compilation, and bundling across your sites and functions. Runtime specifications are unaffected by this change.
+
+{% arrow_link href="/docs/advanced/billing/compute" %}
+Learn more about compute specifications
+{% /arrow_link %}
diff --git a/src/routes/docs/advanced/billing/compute/+page.markdoc b/src/routes/docs/advanced/billing/compute/+page.markdoc
index 6b3ee356e3..c965fff43d 100644
--- a/src/routes/docs/advanced/billing/compute/+page.markdoc
+++ b/src/routes/docs/advanced/billing/compute/+page.markdoc
@@ -10,19 +10,22 @@ These options help you tune performance and cost: for example, a large install o
 
 # Specifications {% #specifications %}
 
-Appwrite Cloud offers the following specification tiers. The same tiers are available for **build** and **runtime** independently on each function or site:
-
-| Memory | CPU cores | Hourly usage |
-|--------|-----------|--------------|
-| 512MB  | 0.5       | 0.25         |
-| 512MB  | 1         | 0.5          |
-| 1GB    | 1         | 1            |
-| 2GB    | 2         | 4            |
-| 4GB    | 2         | 8            |
-| 4GB    | 4         | 16           |
+Appwrite Cloud offers the following specification tiers. You can set **build** and **runtime** specifications independently on each function or site:
+
+| Memory | CPU cores | Hourly usage | Available for     |
+|--------|-----------|--------------|-------------------|
+| 512MB  | 0.5       | 0.25         | Runtime           |
+| 512MB  | 1         | 0.5          | Runtime           |
+| 1GB    | 1         | 1            | Runtime           |
+| 2GB    | 2         | 4            | Build and runtime |
+| 4GB    | 2         | 8            | Build and runtime |
+| 4GB    | 4         | 16           | Build and runtime |
+| 4GB    | 8         | 32           | Build and runtime |
+| 8GB    | 4         | 32           | Build and runtime |
+| 8GB    | 8         | 64           | Build and runtime |
 
 {% info title="Note" %}
-On Appwrite Cloud, **Pro** plan organizations can change build and runtime specifications from the default 512MB and 0.5 CPU. The Free plan uses the default. For custom compute options, contact our [sales team](https://appwrite.io/contact-us/enterprise).
+On Appwrite Cloud, **Pro** plan organizations can change build and runtime specifications from the defaults: 2GB and 2 CPU for builds, and 512MB and 0.5 CPU for runtime. The Free plan uses the defaults. For custom compute options, contact our [sales team](https://appwrite.io/contact-us/enterprise).
 {% /info %}
 
 # Build timeouts {% #build-timeouts %}
diff --git a/src/routes/docs/products/functions/functions/+page.markdoc b/src/routes/docs/products/functions/functions/+page.markdoc
index d8bdced0bb..3517c03efb 100644
--- a/src/routes/docs/products/functions/functions/+page.markdoc
+++ b/src/routes/docs/products/functions/functions/+page.markdoc
@@ -105,7 +105,7 @@ These are terminal commands that will be executed in the runtime containers in t
 
 ## Resource limits {% #resource-limits %}
 
-Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while your deployment is being built and packaged; the runtime spec applies to each function execution. Both use the same CPU and memory tiers on Cloud. This lets you align compute with heavy dependency installs or compilation without over-provisioning every invocation.
+Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while your deployment is being built and packaged; the runtime spec applies to each function execution. On Cloud, builds run on at least 2 CPU cores and 2GB of memory. This lets you align compute with heavy dependency installs or compilation without over-provisioning every invocation.
 
 On Appwrite Cloud, customizing specifications requires the **Pro** plan. See [Compute](/docs/advanced/billing/compute) for tiers, GB-hours, and pricing.
 
diff --git a/src/routes/docs/products/sites/develop/+page.markdoc b/src/routes/docs/products/sites/develop/+page.markdoc
index fba0eb17a1..c66bee1cb3 100644
--- a/src/routes/docs/products/sites/develop/+page.markdoc
+++ b/src/routes/docs/products/sites/develop/+page.markdoc
@@ -47,7 +47,7 @@ The default timeout is set at `15 seconds` and the maximum value possible is `30
 
 # Resource limits {% #resource-limits %}
 
-Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while dependencies are installed and your site is built for deployment; the runtime spec applies when your site serves traffic, including server-side rendering (SSR). Both use the same CPU and memory tiers on Cloud.
+Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while dependencies are installed and your site is built for deployment; the runtime spec applies when your site serves traffic, including server-side rendering (SSR). On Cloud, builds run on at least 2 CPU cores and 2GB of memory.
 
 On Appwrite Cloud, customizing specifications requires the **Pro** plan. See [Compute](/docs/advanced/billing/compute) for tiers, GB-hours, and pricing.