Skip to content
PluginStats

vscode-pydata-viewer installs statistics

By Percy (3 listings) · VS Code Marketplace · Other

Display PyData files (.npz .npy .pkl .pth) in VSCode.

View on VS Code Marketplace Fresh · Oct 19, 2026

vscode-pydata-viewer has 125,991 recorded installs on VS Code Marketplace, ranking #2071 of 2,501 tracked listings.

Installs
125,991
Official API · Oct 19, 2026
7-day growth
—
Insufficient history
30-day growth
—
Insufficient history
90-day growth
—
Insufficient history
Rank
#2071
Among tracked VS Code Marketplace listings

Rating: 5.00 / 5 from 3 ratings

About vscode-pydata-viewer

PyData Viewer

Display Python data files in VSCode.

Supported File Types

• Numpy Files: .npz .npy • Pickle Files: .pkl .pck .pickle .pkl.gz • PyTorch Files: .pth .pt .ckpt

Quick Start

  1. Install the extension from VS Code marketplace 2. Open any supported data file in VS Code 3. The file will automatically display with formatted content

Requirements

:pushpin: Python interpreter is required. Add Python to your system PATH or configure a custom Python path in the extension settings.

Configuration

Extension Settings

• vscode-pydata-viewer.pythonPath: Path to Python interpreter (default: "default") • vscode-pydata-viewer.scriptPath: Path to custom processing script (default: "default")

Python Path Setup

  1. Open VS Code Settings (Cmd+, or Ctrl+,) 2. Search for "pydata viewer" 3. Set Python Path: • System Python: Leave as "default" • Virtual Environment: /path/to/venv/bin/python • Conda Environment: /path/to/conda/envs/myenv/bin/python

Handling Local Imports

If your pickle files contain custom classes from your project, you have these options:

Option 1: Custom Processing Script

Create a custom script that imports your modules:

Then set the script path in VS Code settings:

Option 2: Project Environment

Configure the extension to use your project's Python environment:

Option 3: Workspace Settings

For project-specific configuration, create .vscode/settings.json:

Common Issues

"No module named 'your_module'" Error • Use a custom script with proper imports • Set Python path to your project environment • Ensure your virtual environment contains required dependencies

"Python not found" Error • Check Python installation • Set full path to Python executable in settings • Restart VS Code after changing settings

Examples

Basic Usage

Simply open any .npy, .pkl, or .pth file in VS Code.

Custom Objects

Change Log

Please refer to CHANGELOG.md.

Related Extensions

If you don't have Python available but need to view numpy files, try vscode-numpy-viewer.

Description from the VS Code Marketplace listing.

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

vscode-pydata-viewer installs on VS Code Marketplace, last 90 days: 125,991 installs as of Oct 19, 2026.vscode-pydata-viewerInstalls on VS Code Marketplace · Last 90 days125,991installs125.9K125.9K125.9K125.9K126K126K126KJul 21Aug 5Aug 20Sep 4Sep 19Oct 4Oct 19installsobservedarchived (Internet Archive)no observationsOct 16, 2026 – Oct 19, 2026 · 4 observations · Updated Oct…pluginstats.com
vscode-pydata-viewer installs on VS Code Marketplace, last 90 days: 125,991 installs as of Oct 19, 2026.

7/30/90-day growth

vscode-pydata-viewer installs growth on VS Code Marketplace: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.vscode-pydata-viewerInstalls growth on VS Code Marketplace125,991installs now7-day growthinsufficient historyInsufficient history30-day growthinsufficient historyInsufficient history90-day growthinsufficient historyInsufficient historyGrowth vs. nearest observation to each baseline date · Updated Oct 19, 2026pluginstats.com
vscode-pydata-viewer installs growth on VS Code Marketplace: 7-day growth unavailable, 30-day growth unavailable, 90-day growth unavailable.

Ranking history

vscode-pydata-viewer VS Code Marketplace ranking history: currently #2071 (by installs).vscode-pydata-viewerVS Code Marketplace ranking · by installs · Last 90 days#2071current rank#2069#2070#2071#2072#2073#2074Jul 21Aug 5Aug 20Sep 4Sep 19Oct 4Oct 19rankOct 16, 2026 – Oct 19, 2026 · 4 observations · Updated Oct 19, 2026pluginstats.com
vscode-pydata-viewer VS Code Marketplace ranking history: currently #2071 (by installs).

Ratings over time

vscode-pydata-viewer ratings on VS Code Marketplace, last 90 days: 3 ratings as of Oct 19, 2026.vscode-pydata-viewerRatings on VS Code Marketplace · Last 90 days3ratings2.72.82.933.13.23.3Jul 21Aug 5Aug 20Sep 4Sep 19Oct 4Oct 19ratingsobservedarchived (Internet Archive)no observationsOct 16, 2026 – Oct 19, 2026 · 4 observations · Updated Oct…pluginstats.com
vscode-pydata-viewer ratings on VS Code Marketplace, last 90 days: 3 ratings as of Oct 19, 2026.

Listing placement

All VS Code Marketplace2,501 listings · 126 pages · 1,251 shown · page 104, #11 (overall #2,071)
All VS Code Marketplace: every listing in installs order

Listing placement

Other761 listings · 39 pages · page 32, #5 (overall #625)
Other: every listing in installs order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Installs on a linear scale. Placement is projected from installs, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (4)
Recent installs observations for vscode-pydata-viewer
Date (UTC)InstallsChange vs. previous
125,991+29
125,962+31
125,931+38
125,893—

Similar VS Code Marketplace Other plugins

All 20 vscode-pydata-viewer alternatives

Data source

Install counts, average rating, and rating counts come from the public Visual Studio Marketplace gallery API. Installs are cumulative and exclude updates.

Listing: https://marketplace.visualstudio.com/items?itemName=Percy.vscode-pydata-viewer. First seen Oct 16, 2026; last successful collection Oct 19, 2026. See the methodology.