DynoTable

Export

DynoTable exports query results to CSV, JSON, and NDJSON — from a single selected row up to an entire filtered result set. Large exports run in the background and keep going even if you switch tabs, change profiles, or reload the app.

Open the export dialog with ⌘⇧E, or the Export button in the tab toolbar.

DynoTable's DynamoDB export dialog: output format, the scope of rows to export, and the destination.
DynoTable's DynamoDB export dialog: output format, the scope of rows to export, and the destination.

Formats

  • CSV — one row per item, with headers. Sets serialize as JSON arrays inside a cell (lossy for set semantics, but readable in spreadsheets).
  • JSON — a JSON array of items.
  • NDJSON — newline-delimited JSON, one item per line; ideal for streaming into other tools.

JSON and NDJSON come in two variants:

  • Unmarshalled — plain, readable JSON ("count": 3).
  • (DynamoDB-JSON) — the type-wrapped wire form. Use this when you need a lossless round-trip — it preserves large numbers (> 2⁵³) that the plain variants corrupt. Only available for the full-match scope.

Scopes

  • Currently loaded — the rows currently loaded in the grid.
  • Selection — only the rows you've selected.
  • Full filter match — every item your filter / query matches, streamed straight from DynamoDB (not just what's loaded). A large full-match export bills read capacity for every item — in us-east-1 on-demand, a 4 KB item costs about 1 RCU on a strongly consistent read. Use the pricing calculator to ballpark the cost before you stream millions of rows.

Send the result to the clipboard or save it to a file. Clipboard is only available for the Currently loaded and Selection scopes; Full filter match always writes to a file.

A Smart Table or Workbench result exports as Full filter match only, and the marshalled variant is not offered for Smart Table, Workbench, or PartiQL results. Running those exports needs an active license or trial, like running the queries themselves.

Renamed columns

If you've renamed columns in a tab — or you're exporting a Smart Table with relationship labels — the renamed names flow through to the export. CSV headers and JSON / NDJSON keys use your labels; the underlying data lookup is unaffected. (The marshalled DynamoDB-JSON variant keeps original attribute names for round-trip integrity.)

Background exports

A full-match export of a large table can take a while. Once bytes start flowing, the dialog closes and the export detaches — it shows up in the Activity panel at the bottom of the sidebar with live progress, and it survives closing the tab, switching profiles, and reloading the app (⌘R).

  • Watch progress and cancel from the Activity panel.
  • A finished export raises a toast; click it to reveal the file.
  • Cancelled exports are silent; failed ones stick around with the error message and a Dismiss button — re-run the export to try again.

Export as code

The query you built with the visual filter can leave DynoTable as a program. From a table tab in Visual mode, choose Export as code in the tab toolbar and DynoTable turns the exact request it just ran — the index, the key condition, the filter expression, and the expression attribute names and values — into ready-to-run code for the target you pick:

  • JavaScript / TypeScript — SDK v3 (QueryCommand / ScanCommand), DocumentClient, and a DynamoDB Toolbox program.
  • AWS CLI — an aws dynamodb query or scan command.
  • Python — boto3.
  • Java, Go, .NET, Rust, Kotlin, PHP, Ruby — the typed AttributeValue shapes each SDK expects.
  • PartiQL — the equivalent SELECT statement.

Turn on pagination to wrap the request in a loop that follows LastEvaluatedKey until the result set is exhausted; leave it off for a single page.

DynoTable's Export as code dialog: a visual DynamoDB query rendered as a runnable boto3 program, with the target selector and the pagination toggle.
DynoTable's Export as code dialog: a visual DynamoDB query rendered as a runnable boto3 program, with the target selector and the pagination toggle.

The code comes from the same open-source emitters that power the query builder on this site, so a request that a target cannot express is reported as such rather than rendered as code that looks right and is not.

Export as code covers the visual query or scan of a table tab. A Smart Table, a Workbench query, and a PartiQL statement have no single DynamoDB request to export, so the action is not offered there.

Quick copy

For one-off grabs, right-click a row (or selection) and use Copy as… to put CSV, JSON, NDJSON, or DynamoDB-JSON straight on the clipboard, no dialog.

The AI chat can also start an export for you — ask it to export a table or a query and it produces a downloadable file via the same engine.

Updated