What we saw
next start: the route called request.json() twice.On 16.10.2026 we wrote a Next.js 16.4.2 route that reads await request.json(), logs a field, and then reads request.json() again, the way a logging helper or a validation library might. The first read worked. The second threw TypeError: Body is unusable: Body has already been read, and the route answered 500 with an empty body. In the browser that empty 500 then broke response.json() with “Unexpected end of JSON input”, so the visitor's side shows a different error from the server's.
The same mistake on a response in the browser gave a different message in each engine:
| Where | Message |
|---|---|
| Node 22 and Next.js route handlers | TypeError: Body is unusable: Body has already been read |
| Chromium 152 | TypeError: Failed to execute 'json' on 'Response': body stream already read |
| Firefox 142 | TypeError: Response.json: Body has already been consumed. |
| WebKit 26 (Safari) | TypeError: Body is disturbed or locked |
| Cloudflare Workers (workerd) | TypeError: Body has already been used. It can only be used once. Use tee() first if you need to read it twice. |
We check the Workers row with a test in this site's own code: it reads a body twice in the Workers runtime and compares the error with the row.
Why a body can be read only once
A request or response body is a stream. json(), text(), formData() and arrayBuffer() each read the stream to the end, and after that nothing is left to read. It often happens without a second json() in sight: middleware or an auth helper reads the body first, a console.log(await response.text()) added for debugging sits above the real json(), or a retry reuses the same Response.
Read once, or clone first
Keep the parsed body in a variable and pass it to whatever needs it. If two parts of the code really need the raw stream, call clone() before the first read and give each reader its own copy. The tee() in the Cloudflare message splits the body stream in two, and clone() calls it for you.
export async function POST(request) {
const body = await request.json(); // read once
await logRequest(body); // pass the parsed value on
await saveMessage(body);
return Response.json({ ok: true });
}
// If two places really need the raw body, clone before the first read:
// const copy = request.clone(); const forLog = await copy.text();If the route only forwards a contact form
A route that exists only to pass form fields on to email can be dropped: the form can post straight to Formgong at https://formgong.com/submit, and there is no body of yours to read twice. See the HTML guide.
Frequently asked questions
What does TypeError: Body is unusable mean?
The code tried to read a request or response body that had already been read. A body is a stream and can be read only once.
How do I read a request body twice?
Call request.clone() before the first read and read the copy, or read the body once and pass the parsed value to the code that needs it.
What is the browser version of this error?
Chrome: body stream already read. Firefox: Body has already been consumed. Safari: Body is disturbed or locked.
What does Body has already been used. Use tee() first mean in Cloudflare Workers?
It is the Workers wording of the same error: the code read a request or response body that was already read. Read it once and pass the value on, or call clone() before the first read.
Sources and documentation
Official references for this guide: MDN: Request.clone(), MDN: Response.bodyUsed, Next.js: Route handlers. HTML contact form, where data is stored.
Related guides
- Lovable form submissions to email and Telegram
- HTML contact form without a backend: a working example
- How to send website form submissions to Telegram
- Contact form not sending email? Check where it stops
- Managing website leads in Telegram without a CRM
- Form backend for Lovable, Bolt, v0, Cursor
- Telegram bot for a contact form: build or skip?
- GDPR form backend: 7 checks before you choose
- Lovable form not sending email? 6 fixes
- Netlify Forms not working? React and Bolt fixes
- Stop contact form spam without a CAPTCHA
- GitHub Pages contact form: a working setup
- Mailto Form in HTML: Why It Fails and What to Use
- HTML form to Google Sheets: 2 free methods
- Webflow form submission limit: what to do at 50
- Turnstile vs reCAPTCHA vs hCaptcha for forms
- Contact Form 7 and Elementor forms to Telegram
- Squarespace contact form not sending email?
- Shopify contact form: where do messages go?
- Google Form to Telegram: free Apps Script way
- Wix contact form not sending email? Fixes
- EU / GDPR Formspree alternatives compared
- HTML form action attribute explained
- How do HTML forms work? The HTTP request
- Types of Injection Attacks on Web Forms (2026)
- Indirect Prompt Injection in MCP
- MCP Rug Pull Attack: Detect Tool Changes
- Form without a backend: 7 ways that work
- Thank-you page after form submission (HTML)
- Indirect Prompt Injection Examples (2023–2026)
- Indirect Prompt Injection via Email
- What Is Tool Poisoning in MCP?
- WordPress contact form without a plugin
- Send email from frontend JavaScript
- How to Prevent Indirect Prompt Injection
- Honeypot Form Field: How to Add One That Works
- Contact Form with File Upload (HTML, No PHP)
- Angular contact form without a backend
- Send form submissions to Slack or Discord without Zapier
- Verify a form webhook signature (HMAC-SHA256)
- Contact forms that send nothing: 793 AI-built sites tested
- v0 contact form that actually sends: 3 ways
- How we tested AI-built contact forms, and 12 bugs we hit
- Cloudflare vs Netlify free plan: hosting that never pauses
- EmailJS 412 “Gmail_API: Invalid grant”: reconnect Gmail
- Resend “You can only send testing emails”: verify a domain
- Supabase Edge Function blocked by CORS policy: 3 causes
- Formspree “Form not found” and other errors: fixes
- Web3Forms errors: “Invalid access key” and 403 explained
- How to add customer reviews to your website for free
- Getform not working? “This form has been deleted” and more
- Next.js contact form not working? 6 errors, reproduced
- Webflow form not sending email? What to check, tested
- FormSubmit not working? “This form needs Activation” fix
- Contact form “TypeError: Failed to fetch”: causes and fixes
- WooCommerce product enquiry form
- Contact Form 7 vs WPForms
- Gravity Forms alternative free
- WordPress contact form block
- 535-5.7.8 Username and Password not accepted (Gmail)
- 535 5.7.3 Authentication unsuccessful: Office 365 SMTP
- Nodemailer “Missing credentials for "PLAIN"”: the fix
- Nodemailer “Greeting never received”: port 465 fix
- Nodemailer SSL “wrong version number”: the port fix
- Nodemailer “self-signed certificate in certificate chain”
- Nodemailer ECONNREFUSED 127.0.0.1:587: missing SMTP host
- SendGrid “authorization grant is invalid”: 401 fix
- Mailgun 401 Forbidden: why the API rejects your key
- “Edge Function returned a non-2xx status code”: the fix
- Next.js “Body exceeded 1 MB limit”: Server Action fix
- Unexpected token '<', "<!DOCTYPE "... is not valid JSON
- Turnstile “timeout-or-duplicate” and other siteverify errors
- Turnstile vs hCaptcha vs reCAPTCHA: speed and size tested
- Judge.me reviews not showing on Shopify: how to fix it
- Judge.me review carousel not showing: how to fix it
- Yotpo reviews not showing on Shopify? Check the app embed
- Loox reviews not showing on product page: how to fix
- Shopify reviews not showing: what to check first
- How to show reviews on Shopify
- GDPR for website forms: what each type of form needs
- WooCommerce reviews not showing: how to fix it
- Stamped.io reviews not showing on Shopify: how to fix it
- Etsy reviews not showing: why and what to do
- Trustpilot widget not loading: how to fix TrustBox
- Yotpo problems in 2026: what merchants report
- Contact Form 7 “error trying to send your message” fix
- Elementor form “Your submission failed because of an error”
- Framer form not sending email or not working: what to check
- Carrd contact form not working: plans, spam and errors
- Google review link not working: what customers see and why
- tawk.to widget not showing on your website: causes and fixes
- How to add questions and answers to your product page
- “Failed to send a request to the Edge Function”: fixes
- Next.js “Failed to find Server Action”: what it means
- Brevo “unauthorized: Key not found” 401: the fix
- Amazon SES “Email address is not verified”: the fix
- Shopify contact form not working: how to fix it
- Judge.me alternative for WooCommerce after the 2025 shutdown
- Free WooCommerce review plugins compared on the free version
- WooCommerce review reminder emails without a paid plugin
- Add Voice Recording to a Website Form
- Contact Form 7 spam: how to stop it
- WPForms not sending email: how to fix it
- Contact form emails going to spam: how to fix it
- HTML form not submitting: how to fix it
- Contact form not working: how to find the fault
- Webflow form spam: how to stop it
- Website form to Notion: how to set it up
- Website form to WhatsApp: what works and what does not