D1 account storage limit increase update (#23359)

Author: Oxyjun

src/content/docs/d1/platform/limits.mdx

@@ -12,10 +12,10 @@ import { Render, Details } from "~/components";
 | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
 | Databases                                                                                                           | 50,000 (Workers Paid)[^1] / 10 (Free)             |
 | Maximum database size                                                                                               | 10 GB (Workers Paid) / 500 MB (Free)              |
-| Maximum storage per account                                                                                         | 250 GB (Workers Paid)[^1] / 5 GB (Free)           |
+| Maximum storage per account                                                                                         | 1 TB (Workers Paid)[^1] / 5 GB (Free)             |
 | [Time Travel](/d1/reference/time-travel/) duration (point-in-time recovery)                                         | 30 days (Workers Paid) / 7 days (Free)            |
 | Maximum Time Travel restore operations                                                                              | 10 restores per 10 minute (per database)          |
-| Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#how-many-subrequests-can-i-make)) | 1000 (Workers Paid) / 50 (Free)                           |
+| Queries per Worker invocation (read [subrequest limits](/workers/platform/limits/#how-many-subrequests-can-i-make)) | 1000 (Workers Paid) / 50 (Free)                   |
 | Maximum number of columns per table                                                                                 | 100                                               |
 | Maximum number of rows per table                                                                                    | Unlimited (excluding per-database storage limits) |
 | Maximum string, `BLOB` or table row size                                                                            | 2,000,000 bytes (2 MB)                            |

src/content/release-notes/d1.yaml

@@ -5,19 +5,24 @@ productLink: "/d1/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2025-07-01"
+    title: Maximum D1 storage per account for the Workers paid plan is now 1 TB
+    description: |-
+      The maximum D1 storage per account for users on the Workers paid plan has been increased from 250 GB to 1 TB.
+
   - publish_date: "2025-07-01"
     title: D1 alpha database backup access removed
     description: |-
       Following the removal of query access to D1 alpha databases on [2024-08-23](/d1/platform/release-notes/#2024-08-23), D1 alpha database backups can no longer be accessed or created with [`wrangler d1 backup`](/d1/reference/backups/), available with wrangler v3.
 
-      If you want to retain a backup of your D1 alpha database, please use `wrangler d1 backup` before 2025-07-01. A D1 alpha backup can be used to [migrate](/d1/platform/alpha-migration/#5-create-a-new-d1-database) to a newly created D1 database in its generally available state. 
+      If you want to retain a backup of your D1 alpha database, please use `wrangler d1 backup` before 2025-07-01. A D1 alpha backup can be used to [migrate](/d1/platform/alpha-migration/#5-create-a-new-d1-database) to a newly created D1 database in its generally available state.
 
   - publish_date: "2025-05-02"
     title: D1 HTTP API permissions bug fix
     description: |-
       A permissions bug that allowed Cloudflare account and user [API tokens](/fundamentals/api/get-started/account-owned-tokens/) with `D1:Read` permission and `Edit` permission on another Cloudflare product to perform D1 database writes is fixed. `D1:Edit` permission is required for any database writes via HTTP API.
 
-      If you were using an existing API token without `D1:Edit` permission to make edits to a D1 database via the HTTP API, then you will need to [create or edit API tokens](/fundamentals/api/get-started/create-token/) to explicitly include `D1:Edit` permission. 
+      If you were using an existing API token without `D1:Edit` permission to make edits to a D1 database via the HTTP API, then you will need to [create or edit API tokens](/fundamentals/api/get-started/create-token/) to explicitly include `D1:Edit` permission.
 
   - publish_date: "2025-02-19"
     title: D1 supports `PRAGMA optimize`