# Syntax Highlighting for Multipart Form-Data

**URL:** <https://community.postman.com/t/syntax-highlighting-for-multipart-form-data/72570>\
**Category:** Help Hub\
**Tags:** form-data, multipart\
**Created:** [December 15, 2024, 3:42pm UTC](https://community.postman.com/t/syntax-highlighting-for-multipart-form-data/72570 "2024-12-15T15:42:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kejdajar](https://avatars.discourse-cdn.com/v4/letter/k/e5b9ba/32.png) [@kejdajar](https://community.postman.com/u/kejdajar)\
**Post date:** [December 15, 2024, 3:42pm UTC](https://community.postman.com/t/syntax-highlighting-for-multipart-form-data/72570/1 "2024-12-15T15:42:46Z")

</div>

Hello,  
A few years ago, either I or a colleague made a post about this topic, but I can no longer find it. I wanted to circle back to this topic and see if there have been any updates

I frequently work with `multipart/form-data` POST requests that include both JSON payload and file uploads. While Postman does an excellent job with syntax highlighting for raw JSON, I’ve noticed that JSON content within a form-data part in `multipart/form-data` requests doesn’t benefit from syntax highlighting or validation. This makes it harder to work with complex JSON payloads in such requests.

 ![image](https://us1.discourse-cdn.com/getpostman/original/3X/5/4/54f0bab060873407b31d62d4fcd64a7ba16e89e3.png)

I’d like to point out that tools like Insomnia currently offer JSON syntax highlighting within `multipart/form-data` requests, which significantly improves the user experience when dealing with these types of payloads.

 ![image](https://us1.discourse-cdn.com/getpostman/original/3X/b/a/bae89c3d1cd4dc4a14474432b0cbde2039f69614.png)

Are there any plans to introduce JSON syntax highlighting or validation for JSON content in `multipart/form-data` parts in Postman? Adding this feature would bring Postman closer to feature parity with Insomnia for this specific functionality and greatly enhance usability for developers working with mixed content types.

Looking forward to hearing from the team or the community on whether this is on the roadmap.

(For context, I understand that in my specific case, the payload happens to be JSON, but this request could apply to any structured data type that benefits from syntax highlighting.)

Thank you!

---

<div class="post-metadata">

**Author:** ![danny-dainton](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/danny-dainton/32/29401_2.png) [@danny-dainton](https://community.postman.com/u/danny-dainton)\
**Post date:** [December 16, 2024, 1:02pm UTC](https://community.postman.com/t/syntax-highlighting-for-multipart-form-data/72570/2 "2024-12-16T13:02:54Z")

</div>

Hey @kejdajar 👋

Welcome to the Postman Community! :postman:

I also remember being part of a similar discussion a while ago around syntax highlighting with those text field that happen to be JSON.

> <https://github.com/postmanlabs/postman-app-support/issues/9700>
>
> \*\*Is your feature request related to a problem? Please describe.\*\*
> Need a highl…ighter for JSON format while editing it in the value section under \_\_ body -\> form-data -\> value. Please refer to the below screenshot for the same.
> \<img width="567" alt="Postman - Agent 2021-03-09 10-42-42 png 2021-03-09 12-59-11" src="https://user-images.githubusercontent.com/52168965/110434076-5ce88b80-80d7-11eb-9292-4c79d8b1288e.png"\>
> 
> \*\*Describe the solution you'd like\*\*
> Highlighter for JSON format will help in understanding, viewing the code more efficiently.

Could you provide this feedback on the ticket to keep that information central?

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\
**Post date:** [January 15, 2025, 1:03pm UTC](https://community.postman.com/t/syntax-highlighting-for-multipart-form-data/72570/3 "2025-01-15T13:03:53Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.