IPFS Uploader

WHAT IT DOES

IPFS Uploader allows you to upload text data to the InterPlanetary File System (IPFS) using public gateways. Enter any text — a message, JSON metadata, a markdown file, or any string — and the tool uploads it to IPFS via Web3.Storage or Pinata's public API. The tool returns a Content Identifier (CID) that uniquely identifies your content, a shareable gateway URL (https://ipfs.io/ipfs/{cid}), the file size in bytes, and the upload timestamp. This is essential for developers uploading NFT metadata, storing decentralized application data, sharing immutable content, or learning how IPFS content addressing works.

HOW TO USE

Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Enter the text you want to upload in the text area — this can be plain text, JSON, markdown, or any UTF-8 encoded string. Click "Upload to IPFS" to start the upload process. The tool will attempt to upload your data using Web3.Storage's public HTTP API. If that fails, it will fall back to Pinata's public API. Results display the upload status, the CID, a clickable IPFS gateway URL, the file size in bytes, and the upload time. A progress bar shows the upload progress. Click "Load sample" to load a random sample of data (plain text, JSON, or markdown) for testing. The data is uploaded to public IPFS gateways and is accessible to anyone with the CID.

TECHNICAL MECHANISM

The tool uploads data to IPFS using public HTTP APIs provided by Web3.Storage and Pinata. It encodes the text as UTF-8 bytes using a TextEncoder, then sends a POST request to the Web3.Storage upload endpoint with the binary data. The response contains the CID (Content Identifier) that uniquely identifies the uploaded content. If Web3.Storage is unavailable, the tool falls back to Pinata's pinning API, which requires API keys (demo keys are used for demonstration purposes — in production, you would use your own API keys). The tool uses the Content-Type header to indicate the data is binary and accepts JSON responses. The CID is extracted from the response and displayed along with a gateway URL. Progress tracking is simulated based on the upload stages. All operations are performed client-side — no data is stored or logged beyond the current session. The tool does not require an API key for basic functionality (using Web3.Storage's public endpoint with generous rate limits).

WHAT IT CANNOT SEE

The tool cannot guarantee permanent file storage without using a pinning service or paying for persistence — files uploaded to public gateways may be garbage-collected over time. It cannot upload files larger than the gateway's size limits (typically 100MB to 1GB depending on the service). It cannot provide encryption or privacy for uploaded files — all content is public and can be accessed by anyone with the CID. It cannot retrieve or pin files uploaded through other gateways without the CID — the CID is required to access the file. It cannot upload directories or nested folders without additional tooling (e.g., IPFS directory format, CAR files). It cannot upload binary files (images, videos, PDFs) — only text data is supported in this version. It cannot guarantee the availability of the uploaded content — public gateways may have downtime or rate limits. The tool does not interact with the blockchain for IPFS operations.

PLEASE NOTE

This tool works exclusively with EVM-compatible chains for the wallet connection, but the IPFS upload itself is chain-agnostic and works in the browser regardless. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported for wallet connection but the upload works regardless. Uploaded content is public and accessible to anyone with the CID. For permanent storage, consider using a pinning service like Pinata, Web3.Storage, or Filecoin. The tool does not store any data — all operations are performed client-side. The tool is provided as-is with no warranty or liability. Always verify the CID and gateway URL before sharing. This is not a substitute for professional storage solutions.