Clipboard & Export
Copy or export results in exactly the shape you need — value lists, TSV, CSV, JSON, SQL INSERT, Markdown.
The Clipboard Is the Export (for Results)
For query results, the grid selection is the export. Select what you need and copy; the format adapts to what you selected:
| Selection | Shortcut | Clipboard contents |
|---|---|---|
| One column | Ctrl+C | Plain value list, one per line |
| Several columns | Ctrl+C | TSV with a header row by default — pastes straight into Excel or Google Sheets; CSV, JSON or SQL INSERT if you say so in Options → Results → Export & Copy |
| Rows | Ctrl+Shift+C | The selected rows as JSON |
| Whole table | Ctrl+A, then Ctrl+C | Everything, spreadsheet-ready |
| One cell | Double-click | Just that value |
How to: get query results into Excel
- Run your query and click the first column header you want
Ctrl+Clickany additional headers — selected columns highlight- Press
Ctrl+C, switch to Excel or Google Sheets, and paste — columns and the header row land in separate cells - For the whole table: click any cell, press
Ctrl+A, thenCtrl+C
How to: turn results into a WHERE ... IN clause
- Select the cells or the column with the values you need
- Right-click the selection and choose SQL IN list
- Paste into your query — values arrive quoted correctly per type, e.g.
('a', 'b', 'c')
Right-Click Formats
The context menu adds formats for specific destinations:
- SQL IN list — selected values as
('a', 'b', 'c'), quoted correctly per type, ready to paste into aWHERE ... IN - SQL INSERT — one
INSERT INTO "table" (...) VALUES (...)per row, named after the table the result came from - CSV — with the delimiter and quote from your settings
- Markdown table — for docs, tickets and pull requests
Copy & Export Defaults
Options → Results → Export & Copy decides the shape once, so you stop reformatting after every paste:
| Setting | Default | Choices |
|---|---|---|
| Ctrl+C on several columns | TSV | TSV, CSV, JSON, SQL INSERT |
| CSV delimiter and quote | , and " | comma, semicolon (Excel in most of Europe), tab; double or single quote |
| Header row | on | on / off |
| JSON indent | 2 spaces | 2, 4, one line — also for the collection export below |
| Byte-order mark on CSV/TSV files | on | on / off — Excel needs it to read ä as ä |
One column always copies as a plain list, whatever the format, because that is what pastes
into an IN (...). A field is quoted only when it holds the delimiter, the quote or a
line break.
Export a Result to a File
The Export button in the results toolbar writes the table — the selection when you have one — to a CSV, TSV, JSON or SQL file through the normal save dialog, in the same shape the clipboard would get. JSON and SQL never carry a byte-order mark.
Export or Import a Whole Collection (MongoDB)
For moving entire MongoDB collections, right-click the collection in the sidebar:
- Export to JSON — writes the whole collection to a file via a native save dialog, streamed so large collections don't exhaust memory
- Import from JSON — loads documents from a JSON file into the collection
Connection URIs
Connections move in and out as URIs. Paste any of the five schemes
(mongodb://, mongodb+srv://, postgresql://,
mssql://, aerospike://, clickhouse://) into the
Import URI field to fill the connection form; the
Export URI field shows the reverse. See
Connection URIs.
Snippets & History
Saved snippets and every entry in your query history can be copied or re-inserted into the editor — your queries are never locked in.
Where Your Data Lives
Snippets, history, workspaces and settings are stored locally in a SQLite database under
%APPDATA%/sutido. Nothing is synced to any cloud.
Tip: For bulk data loading, each engine's native tooling
(e.g. mongoimport, COPY, clickhouse-client) is the
right tool — Sutido is where you explore, verify and fix the data afterwards.