Issue with Escaping Backslashes in Postman Response Display

Hello Postman community,

I’m encountering an issue related to how backslashes are displayed in the Postman response. I’m sending a path from my Node.js server to Postman, and while the path is correctly displayed in the console log of my Node.js application, it appears differently in the Postman response.

Here’s the scenario:

When I print the path using console.log in my Node.js application, it correctly appears as:

\SRV-FLX-DEMO\Imagenes\Demo Electro\240.jpg

However, when I view the same response in Postman, it’s displayed as:

\\SRV-FLX-DEMO\\Imagenes\\Demo Electro\\240.jpg

It seems that Postman is escaping the backslashes with double backslashes in the response display, causing the path to be different from what I expect.

I’ve verified that the path sent from my Node.js server is indeed correct and doesn’t contain duplicated backslashes. So, the issue seems to be related to how Postman interprets and displays the backslashes in its interface.

I’ve checked my Node.js code and it’s sending the correct path. I’ve also tried modifying the display settings in Postman, but haven’t found a solution yet.

Is there a way to configure Postman’s response display to show the backslashes correctly without doubling them? Or is this a known behavior in Postman’s interface?

Any insights or guidance on how to resolve this issue would be greatly appreciated. Thank you!

Best regards, Claudio

Hey @joint-operations-co3!

Thanks for reaching out to the Postman community!

The behavior you’re observing is expected. JSON strings represent control characters using escape sequences. The backslash (\) itself is a control character in JSON strings, and it needs to be escaped by another backslash. That’s why, when displaying JSON in Postman, you see two backslashes (\\) instead of one.

For example, if you’re sending a string from your Node.js server as a JSON response, and the string contains backslashes, it will typically look like this when serialized as JSON:

  "path": "\\Full\\File\\Path\\image.jpg"

However, when you use this string in a JavaScript (or Node.js) environment, it will be interpreted as:


If you are viewing the raw response from your server (say, using tools like curl), you’ll likely see the double backslashes, as that’s the correct JSON representation. Postman is just faithfully showing the raw JSON response it receives.

If you’re returning the path in a non-JSON format, or if you’re sure you’re sending it without double backslashes, you might be encountering a different issue.

However, if this is purely about the visual representation in Postman and not affecting functionality, then it’s just how JSON represents backslashes. You won’t need to make any changes in your application logic as the data being sent and received remains correct.

Hope that clears things up! Let us know if you have any more questions or concerns. :slight_smile:

1 Like

Thank you, Kevin!!!

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