Skip to content
Joel Natividad edited this page May 18, 2026 · 3 revisions

qsv pro

Tier: Beginner

qsv pro is the desktop GUI companion to qsv. If you'd rather drop a file and click around than type into a terminal, qsv pro is for you.

It uses the same qsv engine under the hood (so same speed, same correctness), with a graphical layer on top: drag-and-drop file opening, interactive data exploration, AI assistant, charts, and a pro command in qsv itself that bridges the CLI to the GUI.

What it adds over the CLI

Feature CLI (qsv) qsv pro (GUI)
Open a CSV qsv lens data.csv (TUI) Drag-and-drop into the window
Statistical profile qsv stats --everything Auto-runs on open, displayed as cards
Filter / search qsv search --select X 'pattern' Click filter panel
Pivot qsv pivotp Pivot wizard with drag-target dropzones
Charts external tool Built-in plotting
AI assistant qsv describegpt Conversational sidebar
Export qsv to parquet, qsv to xlsx, … Export menu
Workflow recording Manual shell history Visual Workflow panel

The Workflow panel records every action you take and emits a reproducible script — bridging the GUI experience to a CLI artifact you can commit and re-run.

Download

qsv pro homepage has the download badges. Direct links by platform:

Bridge: the pro command

qsv has a built-in pro command that talks to a running qsv pro instance on the same machine. Two subcommands:

  • qsv pro lens <file> — opens a CSV in csvlens inside an Alacritty terminal (Windows only).
  • qsv pro workflow <file> — imports a file into qsv pro's Workflow panel.
qsv pro workflow ~/Downloads/data.csv
# qsv pro must be running on the same machine.

Accepts CSV, TSV, SSV, TAB, XLSX, XLS, XLSB, XLSM, ODS — qsv pro auto-converts.

See Integrations → qsv pro bridge for the command details.

When to pick qsv pro

Use qsv pro when:

  • You prefer a graphical interface
  • You're onboarding non-technical users who'd struggle with the CLI
  • You want a visual Workflow record of an analysis to share
  • You want charts inline without involving another tool

Stick with the CLI when:

  • You want scriptable, reproducible analytics in CI / Make / shell
  • You're processing data at scale (qsv pro is designed for interactive exploration; the CLI handles 100 GB+ files comfortably)
  • You're inside a notebook (Jupyter / Polars) — embed qsv via subprocess instead

You can switch between them on the same file — qsv pro is just the CLI engine with a UI on top.

Plans

Some features (workflow saving, large file processing, ...) may require a paid plan. See qsvpro.dathere.com for current pricing.

See also

Clone this wiki locally