Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Created by Kemal Djakman
Created on Aug 31, 2026

Feature request: Allow configuring the default document copy format


What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

For my workflow, I frequently copy documents from Compass into an editor or application where valid JSON is required.

Feature request: Please add a Compass setting that allows users to choose the default format used by the main Copy to clipboard button, for example:

  • Shell Syntax

  • Extended JSON (EJSON)

What would you like to see happen?

Describe the desired outcome or enhancement.

Feature request: Allow configuring the default document copy format

After updating MongoDB Compass from version 1.49.4 to 1.49.15, I noticed a change in the document copy behavior.

In Compass 1.49.4, right-clicking a document provided only one option:

Copy document

The copied result used double quotes and could be pasted as JSON.

In Compass 1.49.15, the copy options are now:

  • Copy document as Shell Syntax

  • Copy document as EJSON

I understand that the new Shell Syntax option was introduced in the 1.49.14 release series. The new options are useful, but the main Copy to clipboard button appears to copy the document using Shell Syntax. This produces single quotes, making the result unsuitable when the copied document is needed as valid JSON.

For example:

Shell Syntax:

{
'_id': ObjectId('...'),
'name': 'John'
}

EJSON:

{
"_id": {
"$oid": "..."
},
"name": "John"
}

For my workflow, I frequently copy documents from Compass into an editor or application where valid JSON is required.

Feature request: Please add a Compass setting that allows users to choose the default format used by the main Copy to clipboard button, for example:

  • Shell Syntax

  • Extended JSON (EJSON)

Alternatively, the Copy button could provide a small dropdown allowing the user to select the desired format directly.

This would preserve the convenience of the new Shell Syntax functionality while allowing users who regularly work with JSON to make EJSON their default.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.


What steps, if any, are you taking today to manage this problem?

Instead of using the 'Copy to clipboard' button, I have to right click on the document and choose the format