


Converting FormData to a multipart/form-data String and Back Using Response
While working on another article about converting various values into ReadableStream, I stumbled upon a neat trick to convert FormData into a multipart/form-data string and back using the Response. Surprisingly, FormData doesn't provide this functionality out of the box. However, by leveraging the methods of Response, we can achieve this quite easily.
I even tried to get assistance from ChatGPT (both 4o and o1-preview), but it couldn't suggest or synthesize this solution, even with hints. Google searches didn't yield any results either. It seems this approach is unknown or little-known, though I don't claim originality. I don't think the ability for such conversion was intentionally designed by the authors of the Response API; it's more of a side effect, which makes the solution even more interesting. So, I decided to write this article to share my findings.
Converting FormData to a Multipart/Form-Data String
Let's suppose we have an instance of FormData:
const formData = new FormData(); formData.set('value', 123); formData.set( 'myfile', new File(['{"hello":"world"}'], 'demo.json', { type: 'application/json' }) );
Our goal is to obtain a multipart/form-data string from this FormData instance. Common suggestions involve manually serializing FormData into a string or performing complex manipulations via Request, or using a library for it. However, we can simply use the Response constructor, which accepts FormData as the body, and then call its text() method to get the desired string representation:
// FormData -> multipart/form-data string function convertFormDataToMultipartString(formData) { return new Response(formData).text(); } const multipartString = await convertFormDataToMultipartString(formData); console.log(multipartString); // Example output: // ------WebKitFormBoundaryQi7NBNu0nAmyAhpU // Content-Disposition: form-data; name="value" // // 123 // ------WebKitFormBoundaryQi7NBNu0nAmyAhpU // Content-Disposition: form-data; name="myfile"; filename="demo.json" // Content-Type: application/json // // {"hello":"world"} // ------WebKitFormBoundaryQi7NBNu0nAmyAhpU--
If needed, we can also extract additional values like the Content-Type header and the boundary:
// FormData -> multipart/form-data async function convertFormDataToMultipart(formData) { const response = new Response(formData); const contentType = response.headers.get('Content-Type'); const boundary = contentType.match(/boundary=(\S+)/)[1]; return { contentType, boundary, body: await response.text(), }; } const multipart = await convertFormDataToMultipart(formData); console.log(multipart); // { // contentType: 'multipart/form-data; boundary=----WebKitFormBoundarybfJIH5LgEGPqNcqt', // boundary: '----WebKitFormBoundarybfJIH5LgEGPqNcqt', // body: '------WebKitFormBoundarybfJIH5LgEGPqNcqt\r\n...' // }
Instead of using text(), we can also use other methods like arrayBuffer() to obtain the encoded content of FormData as an ArrayBuffer. The advantage of this type of value is that it's a transferable object and can be efficiently transferred between workers using postMessage() (meaning without copying, unlike a string). The FormData object itself is not transferable.
Converting Multipart/Form-Data String Back to FormData
To reverse the process, we again utilize Response, but this time we use its formData() method. A key aspect of this method is that it requires the correct Content-Type header, which must include the multipart/form-data type and the boundary used to separate the parts. If we have the boundary value, we can insert it into the header. However, we might only have the multipart string and nothing else. In that case, we can extract the boundary from the string using a regular expression.
// multipart/form-data string -> FormData async function convertMultipartStringToFormData(multipartString) { const boundary = multipartString.match(/^\s*--(\S+)/)[1]; return new Response(multipartString, { headers: { // Without the correct header, the string won't be parsed, // and an exception will be thrown on formData() call 'Content-Type': 'multipart/form-data; boundary=' + boundary, }, }).formData(); } const restoredFormData = await convertMultipartStringToFormData(multipartString); console.log([...restoredFormData]); // [ // ['value', '123'], // ['myfile', File] // ]
Just like with serializing FormData, we can convert not only strings but also ArrayBuffer, TypedArray, and ReadableStream into FormData, since Response accepts such values as the body value.
Conclusion
One potential downside is that both types of conversions are asynchronous operations. Other than that, the method seems quite reliable and can be used for debugging or when conversion is needed outside of fetch().
This method has wide browser support (it should work in any browser released after 2017). The method is also applicable in Node.js, Deno, and Bun if they support the Response object (i.e., versions where fetch() is available).
I hope you find this approach as intriguing as I did. It's a simple yet effective way to convert FormData to a multipart/form-data string (and not only a string) and back, leveraging the capabilities of the Response API. If you have any thoughts or know of other methods to achieve the same result, feel free to share in the comments!
The above is the detailed content of Converting FormData to a multipart/form-data String and Back Using Response. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











JavaScript is the cornerstone of modern web development, and its main functions include event-driven programming, dynamic content generation and asynchronous programming. 1) Event-driven programming allows web pages to change dynamically according to user operations. 2) Dynamic content generation allows page content to be adjusted according to conditions. 3) Asynchronous programming ensures that the user interface is not blocked. JavaScript is widely used in web interaction, single-page application and server-side development, greatly improving the flexibility of user experience and cross-platform development.

The latest trends in JavaScript include the rise of TypeScript, the popularity of modern frameworks and libraries, and the application of WebAssembly. Future prospects cover more powerful type systems, the development of server-side JavaScript, the expansion of artificial intelligence and machine learning, and the potential of IoT and edge computing.

Different JavaScript engines have different effects when parsing and executing JavaScript code, because the implementation principles and optimization strategies of each engine differ. 1. Lexical analysis: convert source code into lexical unit. 2. Grammar analysis: Generate an abstract syntax tree. 3. Optimization and compilation: Generate machine code through the JIT compiler. 4. Execute: Run the machine code. V8 engine optimizes through instant compilation and hidden class, SpiderMonkey uses a type inference system, resulting in different performance performance on the same code.

Python is more suitable for beginners, with a smooth learning curve and concise syntax; JavaScript is suitable for front-end development, with a steep learning curve and flexible syntax. 1. Python syntax is intuitive and suitable for data science and back-end development. 2. JavaScript is flexible and widely used in front-end and server-side programming.

JavaScript is the core language of modern web development and is widely used for its diversity and flexibility. 1) Front-end development: build dynamic web pages and single-page applications through DOM operations and modern frameworks (such as React, Vue.js, Angular). 2) Server-side development: Node.js uses a non-blocking I/O model to handle high concurrency and real-time applications. 3) Mobile and desktop application development: cross-platform development is realized through ReactNative and Electron to improve development efficiency.

This article demonstrates frontend integration with a backend secured by Permit, building a functional EdTech SaaS application using Next.js. The frontend fetches user permissions to control UI visibility and ensures API requests adhere to role-base

The shift from C/C to JavaScript requires adapting to dynamic typing, garbage collection and asynchronous programming. 1) C/C is a statically typed language that requires manual memory management, while JavaScript is dynamically typed and garbage collection is automatically processed. 2) C/C needs to be compiled into machine code, while JavaScript is an interpreted language. 3) JavaScript introduces concepts such as closures, prototype chains and Promise, which enhances flexibility and asynchronous programming capabilities.

I built a functional multi-tenant SaaS application (an EdTech app) with your everyday tech tool and you can do the same. First, what’s a multi-tenant SaaS application? Multi-tenant SaaS applications let you serve multiple customers from a sing
