OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Arloader

Arloader is an open-source Rust command-line application and client for uploading local files to Arweave. It reads files asynchronously, prepares bundles in parallel across multiple threads, and posts them to arweave.net. Its documented workflows cover general file uploads, cost estimates, and NFT asset and metadata uploads that create manifests and update metadata links.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Arloader — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Arloader when a command-line workflow is suitable for moving local files to Arweave, especially for batches or NFT asset-and-metadata sets.

Who it is for

  • Developers publishing files or application assets to Arweave.
  • NFT creators preparing and uploading asset files with JSON metadata.
  • Rust developers looking for a client for Arweave file uploads.

Documented uses

  • Estimate the upload cost for selected local files.
  • Upload a batch of files to Arweave, using bundles where suitable.
  • Upload NFT assets and metadata, then locate the generated manifest links.
  • Choose between AR-funded and documented SOL-funded transaction workflows.
Before you choose

Requirements & limits

The README offers Linux and Mac release binaries, or Cargo installation with Rust nightly. Upload workflows require wallet credentials and the relevant AR or SOL funding method.

  • The tool is a CLI and Rust client, not a hosted upload interface.
  • The documented default bundle size is 100 MB and the maximum is 200 MB; larger files can be sent individually.
  • AR funding and SOL-funded transactions are documented as separate choices with different wallet prerequisites.
  • The NFT workflow can create manifests and update metadata links as part of the upload process.
  • The repository lists an Apache-2.0 license.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare and upload a batch of files

Estimate the upload cost and start an Arweave upload for selected local files.

Before you start

  • Arloader installed from a Linux or Mac binary, or through Cargo with Rust nightly.
  • An Arweave wallet JSON file.
  • AR tokens for AR-funded transactions, or a Solana wallet JSON file and SOL when using SOL funding.
  • Local files to upload.

Steps

  1. Run arloader estimate to request an estimate for the selected paths; paths can be a glob or multiple files.

  2. Run arloader upload to begin uploading the files.

  3. For files larger than 100 MB but under 200 MB, specify a larger bundle size; use --no-bundle for files larger than 200 MB.

  4. For SOL-funded transactions, add the documented --with-sol option and use a Solana keypair; otherwise configure the AR keypair for AR-funded transactions.

Expected outcome

Arloader starts sending files in bundles where applicable, or as individual files when bundling is disabled.

Guide limitations

  • The README documents bundle sizes up to 200 MB, with a default of 100 MB; files over 200 MB are uploaded individually.
  • The guide describes starting an upload, not a guaranteed transaction confirmation time or result.
Documentation 1 ↗
Source-based practical guide

Upload NFT assets and metadata

Upload NFT media and JSON metadata using the documented `upload-nfts` workflow.

Before you start

  • Arloader installed and a folder containing each NFT's asset file or files and associated .json metadata.
  • An Arweave keypair and AR funding, or a Solana keypair and SOL funding.

Steps

  1. Place asset files and their associated JSON metadata files in a dedicated folder.

  2. Run arloader upload-nfts --ar-keypair-path for AR funding, or use the documented SOL flags and keypair path for SOL funding.

  3. Review the generated arloader_ directory, where upload statuses and manifest files are recorded.

  4. Use the generated metadata manifest to find links to the uploaded metadata files.

Expected outcome

The workflow uploads assets and metadata, creates manifests, and updates metadata with links to uploaded assets.

Guide limitations

  • The documented workflow assumes image and metadata pairs for the NFT assets.
  • The README notes that --link-file selects manifest-path links instead of the default bundle-item ID links.
  • The guide documents command usage and outputs; it does not guarantee confirmation timing.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
CalebEverett/arloader · Official homepage title · retained in its source language
How we review sourcesSuggest a correction