The clone() method of the Request interface creates a copy of the current Request object.

Like the underlying ReadableStream.tee api, the body of a cloned Response will signal backpressure at the rate of the faster consumer of the two bodies, and unread data is enqueued internally on the slower consumed body without any limit or backpressure. Beware when you construct a Request from a stream and then clone it.

clone() throws a TypeError if the request body has already been used. In fact, the main reason clone() exists is to allow multiple uses of body objects (when they are one-use only.)

If you intend to modify the request, you may prefer the Request constructor.





Return value

A Request object, which is an exact copy of the Request that clone() was called on.


In the following snippet, we create a new request using the Request() constructor (for an image file in the same directory as the script), then clone the request.

const myRequest = new Request('flowers.jpg');
const newRequest = myRequest.clone(); // a copy of the request is now stored in newRequest


Fetch Standard
# ref-for-dom-request-clone①

Browser compatibility

BCD tables only load in the browser

See also