Parquet viewer
and editor.

Local data viewer · Windows and macOS

Explore local Parquet files and supported dataset folders on Windows and macOS. Inspect schemas, select columns and query records. Stage supported edits and save a separate copy for bounded columnar sources.

Free Preview: up to 100 read-only records. No account or card.
Version 0.1.1 · Windows x64 · macOS Apple Silicon · Install guide →

Inspect columnar data without a cloud upload

A feature export, training split or partitioned market history often needs a focused inspection before a larger analysis. RowCove lets you choose a local file or dataset folder, review the detected reader and begin with useful records.

Free Preview needs no account and returns a read-only first page of up to 100 records where the reader permits. It can help establish the source structure and types. Pro adds supported query and output workflows; a complete folder-wide aggregate is a separate requirement, not something inferred from a visible page.

Use the schema to choose columns

Parquet's columnar layout makes the required fields part of the access decision. Project the columns that answer the question rather than decoding unrelated text, features or wide nested structures. Inspect exact values and returned types before comparing them with another source.

For market data, verify timestamp units, timezone and price precision. For training features, check identifiers, split meaning and nested values. These example choices use synthetic mock data only.

Parquet inspection choices · synthetic (mock) data
QuestionSelected fieldsMock scope
Inspect a price recordsymbol, timestamp, closeDEMO-A · one day
Check a training examplerecord_id, text, splitmock_001 · demo split
Compare feature typesrecord_id, feature_scoresynthetic features

Select partitions before expanding the scan

Open a supported Parquet dataset folder to discover its shards and recognized Hive-style partitions. A folder layout such as split=demo or year=2026/month=01 can expose partition values that help scope the task. Only recognized predicates can support pruning; not every arbitrary filter avoids reading a file.

  1. Choose the intended dataset root and version.
  2. Review partitions and select the smallest useful scope.
  3. Project the fields required for the result.
  4. Browse bounded pages and preserve any continuation cursor.
  5. Keep source-file provenance with findings.

Schema differences across shards need investigation. Bounded discovery does not establish complete schema reconciliation, global ordering, an exact total row count or a global aggregate. Follow the partitioned Parquet and Arrow tutorial for the scope and continuation rules.

Match performance expectations to the operation

Column selection and supported partition pruning can reduce unnecessary data access and decoding. They do not make every full scan or sort instantaneous. Storage, compression, nested values, partition layout and the selected task still affect latency and resource use.

The published 20 GB CSV comparison measures CSV, not Parquet throughput. Use the performance model and test a representative local source before expanding a job. For very large collections, the TB-scale access planning guide covers fields, scan scope, memory and disk budgets.

Continue with a deliberate local workflow

The Parquet reader supports schema inspection, projection, bounded filtering/sorting and supported new-artifact workflows. For a supported bounded source, use Pro to stage cell edits and Save copy to a new destination. Parquet and Arrow edit-copy currently require a source no larger than 128 MiB, with at most 200,000 rows and 512 columns. Inspection and query support do not make a larger source editable. Dataset-folder browsing is read-only; open an eligible individual shard for a correction. Check the columnar editing limits and steps before buying Pro for this task. Arrow IPC and Feather have their own columnar readers; a CSV viewer workflow and a JSONL record workflow have different access costs and semantics.

Use authorized local MCP tools when you want an assistant to request a small result. Dataset processing stays local, while returned tool results are shared with the connected client. Review format-specific capabilities and the introductory offer and standard Pro renewal terms before committing to a larger workflow.

Try the first page on your own data.

Start on Windows or macOS: source information and up to 100 records, read-only. Review reader capabilities before planning a full-file Pro workflow.

Version 0.1.1 · Windows x64 · macOS Apple Silicon · Install guide →

Reader capabilities →

Parquet columns, partitions and resources

Questions, answered

Contact support →
Does selecting Parquet columns or partitions skip all other data?

Selecting required columns can reduce column decoding. Recognized Hive-style partition predicates can also avoid unrelated shards in supported dataset folders. A general row filter is different: it does not guarantee that every irrelevant file, row group or byte is skipped.

Choose a narrow partition scope and required fields, inspect the returned types, then continue bounded pages while a cursor is present. The result does not imply a global sort, complete schema reconciliation, global aggregate or exact dataset-wide count. Use the source information and operation scope shown by the detected reader.

Explore the local Parquet viewer Follow the partitioned dataset workflow

How do I open JSONL, Parquet or Arrow data split across many files?

Use the folder picker or drop a dataset folder into Open data. For supported collections, RowCove discovers shards and available split or partition information. Choose the relevant source scope, project the fields you need and browse bounded result pages with source context.

Keep the scope explicit when comparing results: one split, a date partition and the entire collection are different populations. Follow the continuation state through pages when you need every matching record. A bounded collection scan should not be treated as an automatic global sort, aggregate or complete schema reconciliation across every shard.

Browse a pretraining shard collection Work with columnar datasets

Does RowCove load the entire file into RAM?

The desktop renders bounded pages, and the native readers can work with selected fields or partitions instead of placing every record in the visible table. This reduces the work needed for browsing, but it does not establish a fixed memory ceiling for every operation.

Index preparation, full-file filtering, sorting, very wide records and large nested values have different resource costs. Temporary disk may also be used. Measure the actual operation on your source and leave room for query work and output copies, especially when working near the limits of your device.

Understand the performance model Plan memory and disk usage