Runpod Network Volume Explorer

A graphical file browser for Runpod Network Volumes using the S3-compatible API.

This is designed to get around some of the obstacles faced when using other GUI projects for AWS S3 services as these tend to use obscure API parameters and settings that break when connecting to a Runpod endpoint. By using known, documented endpoints supported by Runpod's Network Volumes to emulate a familiar File Explorer experience, this will provide a really easy, reliable way to interface with your files without having a running Pod to reduce spend while you setup your projects.

Features

• Browse files and folders on your Runpod Network Volume
• Upload files and folders (with extension filter and conflict handling)
• Download files and folders (with progress tracking)
• Create new folders
• Rename, cut/paste (move), and delete files/folders
• Edit text files directly with built-in editor
• Open files with system default applications (Linux-only support)
• Multi-threaded transfers for better performance

Requirements

AWS CLI must be installed and configured on your system.

1. Install AWS CLI:

   • Linux: sudo apt install awscli (or use your package manager)
   • Windows: Download from https://aws.amazon.com/cli/

2. Configure AWS CLI with your Runpod S3 API credentials:

   a) Go to https://www.runpod.io/console/user/settings
   b) Expand "S3 API Keys" and create a new key
   c) Save the access key (user_...) and secret (rps_...)

   d) Run in terminal:
   aws configure

   e) Enter when prompted:

   • AWS Access Key ID: Your user ID (e.g., user_2f21CfO73Mm2Uq...)
   • AWS Secret Access Key: Your S3 API secret (e.g., rps_...)
   • Default Region: (leave blank)
   • Default output format: (leave blank or json)

Running the Application

Check out the releases and download the relevant version for your operating system

Linux:
./RunpodVolumeExplorer or double-click from file explorer

Windows:
Double-click RunpodVolumeExplorer.exe

First Time Setup

1. Launch the application
2. Select your datacenter from the dropdown (or choose Custom for other endpoints)
3. Enter your Network Volume ID (found in Runpod Console > Storage)
4. Click "Test Connection" to verify everything works
5. Click "Connect" to start browsing your files

Troubleshooting

"AWS CLI not found"

• Make sure AWS CLI is installed and in your system PATH
• Try running aws --version in a terminal to verify

"Access denied"

• Check that your S3 API credentials are correct
• Make sure you're using the S3 API key, not your regular Runpod API key

"Volume not found"

• Verify the Network Volume ID is correct
• Make sure you selected the correct datacenter

"Connection timed out"

• Check your internet connection
• The Runpod S3 API may be temporarily unavailable