Web3 Files Network

Permanent Names Structure (IPFS)

Permanent Names create a structured naming layer on top of IPFS so you can retrieve content with simple, human-readable references instead of passing long CIDs around.
In Web3 Files, files are retrieved by nickname (no extensions), and folders are user-defined.

~NAME
IPFS FOLDERS
FILE NICKNAMES
ATTRIBUTES
METADATA
Name: ~myname
Path: ~myname.ipfs.folder.nickname
Metadata: ~myname.ipfs.folder.nickname.$meta

What Permanent Names provide

Permanent Names are a function-based naming system: ~name.function. Web3 Files uses the ipfs function to map your folder structure and file nicknames to IPFS CIDs.

Name structure: folders + nicknames

The IPFS function is designed for easy retrieval. After ipfs, the system treats everything as user-defined folder names and file nicknames.

Retrieve file content: ~myname.ipfs.Marketing.CyberBarPosterJan2026
Retrieve metadata (JSON): ~myname.ipfs.Marketing.CyberBarPosterJan2026.$meta
List a folder: ~myname.ipfs.Marketing

Reserved action suffixes

$meta Returns the file metadata document (pinned to IPFS as JSON).
$resolve Returns pointers only (content CID, meta CID, MIME, size, timestamps).
$list Optional explicit listing of a folder (same as requesting the folder without a nickname).
$manifest Developer-friendly output for the folder manifest entry (useful for debugging).
How resolution works

Web3 Files can run fully IPFS-native: your library is represented by pinned JSON documents. Permanent Names store only lightweight pointers to the latest CIDs.

  • Permanent Names pointers
    Small, updateable references (latest CIDs)
    • ~name.ipfs.root
      Points to the latest Root Manifest CID
  • Pinned manifests on IPFS
    Immutable JSON documents (new CID each update)
    • Root Manifest
      Maps top folders → Folder Manifest CIDs
    • Folder Manifest
      Maps subfolders + nicknames → file entries
    • File Metadata JSON
      Attributes: title, tags, description, type, privacy intent
    • Content CID
      The actual file stored on IPFS
Simple view: nickname → { content_cid, meta_cid }

Folder manifests hold the mapping between a nickname and the file’s content CID + metadata CID.

Attributes: what metadata contains

Attributes live inside the metadata JSON pinned to IPFS. They enable organization, filtering, discovery, automation, and long-term usability.

Required basics

  • content CID (the file itself)
  • meta CID (the JSON describing the file)
  • size + timestamps
Example: ~myname.ipfs.folder.nickname.$resolve

AI-enhanced fields

  • title and description (human-friendly)
  • tags and topics for filtering
  • optional preview pointers (thumbnail CID)
Returned by: $meta

Folder-level defaults

  • Folders can define default behaviors for new files (visibility intent, tagging conventions, project labels).
  • Teams can keep structure consistent by reusing folder templates.
  • Metadata stays portable because it is pinned to IPFS (CID-based).

Versioning

  • New file content → new content CID.
  • Metadata updates → new meta CID.
  • Folder/Root manifests update to point to the newest entries.

This keeps history clean and traceable while preserving IPFS immutability.

Ready to try it?

Start free now. Build folders, upload to IPFS, and retrieve content using Permanent Names. Upgrade later for advanced metadata and distribution tools.