Web3 Files Network

How Web3 Files Network Works

Web3 Files Network is an easy to use content-addressed storage dashboard.
Upload files to IPFS, and you receive a CID that can retrieve that content reliably without depending on a single server path.

Web2 Paths
Web3 CIDs
Gateways
Folder Structure
Optional Monetization
Web2: domain.com/file.png
Web3: gateway/ipfs/CID
Identity Mapping: ~myname.ipfs.folder.file...
No Code

Traditional storage is “location-based” (server folders, URLs that can break). IPFS is “content-based.” Your file’s identity is its CID.
If the content is the same, the CID is the same. If the content changes, the CID changes.

Step-by-step (the real flow)

Steps 1–3 are your core workflow.
Steps 4–6 are for Creator and Agency memberships.

1 Create your account

Create your account in seconds using your name, email, and a secure access code. * No payment required.

2 Create a folder to store your files

Each folder is a container. They hold your files. Build your primary folder first, then add subfolders up to 5 levels deep.

3 Upload files via File Management

Upload files directly into the folder you created. After each upload, you receive the file’s CID (Content ID), and you can easily move files between folders as your structure evolves.

4 Advanced folder and file settings

Control privacy, sharing, monetization, minting, and other optional advanced settings for your files and folders.

5 Configure special metadata

Attach advanced metadata to your folders and files to enhance organization, discovery, automation, and long-term usability.

6 Distribution, tracking, and engagement

Distribute files and folders with full tracking, shareable links, and insights to monitor access, usage, and delivery across platforms.

Folder structure (up to 5 levels deep)

Folders can be nested up to 5 levels deep. Build a primary folder per project/client, then keep subfolders modular.

  • Level 1 — Primary Folder
    Example: “MyProject”
    • Level 2 — Subfolder
      Example: “assets”
      • Level 3 — Subfolder
        Example: “images”
        • Level 4 — Subfolder
          Example: “promos”
          • Level 5 — Subfolder
            Example: “approved”
          • Level 5 — Subfolder
            Example: “drafts”
      • Level 3 — Subfolder
        Example: “audio”
        • Level 4 — Subfolder
          Example: “albums”
          • Level 5 — Subfolder
            Example: “track-stems”
      • Level 3 — Subfolder
        Example: “keys” (private)
    • Level 2 — Subfolder
      Example: “client-deliveries”
🧠 Pro Tip: Build your complete folder structure first!
We make it easy to organize your folders.

After upload: your CID becomes your shareable superpower

The moment a file lands in Web3 Files Network, you receive a permanent identifier and instant distribution options.

CID Issued instantly
Gateway Link Ready
  • CID returned instantly — a durable identifier that references the content itself (not a server path).
  • Share links generated — publish via our IPFS gateway, or use a leased dedicated gateway for full control and branding.
  • Clean versioning — upload an updated file and it receives a new CID, keeping versions clear and traceable.
  • Folder-level distribution — share one folder link to deliver an organized bundle of files in one shot (plan-based tools).
Example gateway path: https://your-gateway.Web3Files.net/ipfs/<CID>
Share and distribute your files (replace this image anytime)

Advanced Creator + Agency features

Permanent Names Integration

Instead of passing CIDs around, you can reference content through a structured naming layer.

Permanent Names lets you map IPFS content (CIDs) into clear, human-readable references, making your files easier to identify, manage, and rely on over the long term.

Example Mapping: ~myname.ipfs.file-folder.file-nickname
More About Permanent Names - Click Here

This turns long CID identifiers into a structured naming layer so content can be referenced consistently across apps, teams, and platforms.

Monetize with Game Tokens (GTs)

  • Game Tokens are a closed-loop system for Web3 and metaverse platforms.
  • Ideal for virtual goods, NFT based collectables, file access, and unlimited utility models.

Agency payment options

  • Agencies can connect their own payment optionswith custom billing workflows and branded delivery paths.
  • Built for teams managing creators and different assets, with centralized organization.
Ready to try it?

Start free now. Build your folder structure, upload to IPFS, and get your CIDs. Upgrade later for advanced access controls, metadata, Permanent Name mapping, and monetization.

Learn the basics

These quick definitions clarify the difference between Web2 storage paths and Web3 content addressing, and why that matters for metaverse assets.

What is local storage (Web2)?

Local storage (replace image anytime)
  • Web2 storage is location-based: files live on a specific server, host, or cloud bucket.
  • Access is typically a domain name + folder path (the URL is tied to infrastructure and file locations).
  • Links can break when servers change, files move, hosting expires, paths get renamed, or a platform shuts down.
🌐 Typical Web2 URL: https://yourdomain.com/uploads/images/banner.png

In Web2, the address is mainly about where the file lives (domain + path).

What is IPFS (Web3)?

IPFS (replace image anytime)
  • IPFS is content-addressed: the file’s identity is its CID (Content ID).
  • Instead of “domain/path,” Web3 retrieval uses a gateway plus the CID (and IPFS path routing).
  • This makes your reference about what the file is (the content), not where it sits on a server.
🧬 CID (example): bafybeigdyrzt
🚪 Web3 gateway path: https://gateway.yourdomain.com/ipfs/bafybeigdyrzt

In Web3, the gateway is the “front door,” and the CID is the permanent identifier.

Metaverse digital assets (already “NFT-like” by design)

Metaverse digital assets (replace image anytime)
  • In many metaverse platforms, assets already behave like unique NFTs: they have unique IDs and can be owned, transferred, and verified by the platform.
  • In other words: the “NFT part” often already exists — the asset is unique — it just needs to be claimed to your ownership (identity/wallet/account).
  • Once claimed, the ownership state can be recognized across your workflows (distribution, licensing, access, delivery).
🧾 Ownership tracking: Scripted objects can track ownership as the asset transfers to others (creator ID, owner ID, permissions, and transfer events).

This creates real “ownership behavior” even before a blockchain is involved. Web3 Files focuses on storing and distributing the supporting content (textures, posters, audio, documentation, updates) with stable identifiers.

Why IPFS helps metaverse workflows

  • Store posters, textures, product images, audio, documentation, scripts, and deliverables as CID-addressed content.
  • Use gateway links in websites, vendors, HUDs, kiosks, and marketing tools.

Why folders matter for creators/agencies

  • Package “asset kits” as reusable folder containers (versions, promos, docs, keys).
  • Apply privacy/sharing rules at file or folder level.
  • Enable metadata and monetization when ready (membership-based).

Bottom line: metaverse assets are often already unique and trackable. Web3 Files adds the missing operational layer durable storage, clean organization, stable identifiers, and controlled distribution.