Beyond the Profile: How the human.json Protocol Aims to Redefine Your Digital Self

In a web dominated by proprietary platforms and fractured identities, a simple JSON file emerges as a radical proposal for a portable, human-centric digital presence. We analyze the human.json protocol's vision, mechanics, and its potential to reshape our online existence.

Analysis | Published March 9, 2026

The architecture of our online identity is broken. We are fragmented across dozens of platforms—LinkedIn owns our professional self, Twitter/X our public voice, Instagram our curated visuals, and a myriad of apps hold slivers of our data. Our digital identity is not ours; it is a collection of profiles hosted on servers we don't control, governed by terms we rarely read. In response to this systemic issue, a quiet but compelling project has emerged from the developer community: the human.json protocol.

Hosted on Codeberg by developer Robida, the protocol proposes a startlingly simple yet profound concept: a single, standardized JSON file named `human.json` placed in the root of your personal website or domain. This file acts as a canonical, machine-readable, and human-editable source of truth about you—a digital business card for the modern, decentralized web.

Key Takeaways

  • Radical Simplicity: The protocol's power lies in its minimalist, open-standard approach using ubiquitous JSON format, lowering the barrier to adoption.
  • Self-Sovereignty: It shifts control from corporate platforms to the individual, hosted on a personal domain—a foundational principle of the IndieWeb movement.
  • Dual-Purpose Design: The `human.json` file is structured for both easy human reading and direct parsing by bots, APIs, and search engines.
  • Extensible & Modular: While defining core fields like name, bio, and links, the format is designed for custom extensions, allowing it to evolve with needs.
  • Early-Stage Potential: Its success hinges not on technical complexity but on community adoption and the development of a supporting ecosystem of parsers and tools.

Decoding the Protocol: More Than Just a Digital VCard

The specification, as detailed on the project's page, is intentionally lean. A basic `human.json` file might look something like this:

{ "name": "Alex Chen", "bio": "Developer and writer exploring the future of human-computer interaction.", "links": [ { "title": "Blog", "url": "https://alex.example.com" }, { "title": "GitHub", "url": "https://github.com/alexchen" }, { "title": "Mastodon", "url": "https://social.example.com/@alex" } ], "location": "Vancouver, Canada" }

This simplicity is deceptive. While reminiscent of earlier standards like vCard or microformats (h-card), `human.json` distinguishes itself through its modern context and philosophical underpinnings. It's not just a contact file; it's a personal API endpoint. By residing at a predictable location (`https://yourdomain.com/human.json`), it creates a universal lookup mechanism. A search engine bot, a federated social platform, or a new contact's address book app could theoretically all fetch this file to reliably discover and display canonical identity information.

The Historical Context: From FOAF to IndieWeb

The quest for portable identity is not new. The early 2000s saw the Friend-of-a-Friend (FOAF) project, an RDF-based ontology for describing people and their social networks. While philosophically aligned, FOAF struggled with complexity and adoption. The 2010s brought the IndieWeb movement, with principles of "owning your data" and "using web mentions." `human.json` can be seen as a natural, pragmatic evolution of these ideas—swapping RDF's complexity for JSON's universal developer familiarity and leveraging the now-commonplace personal domain.

Analytical Angle: The Protocol as a Bridge

The genius of `human.json` may be its role as a bridge. It connects the static, owned space of a personal website with the dynamic, interconnected social web. It provides a stable anchor point. When you update your bio or profile picture in your `human.json` file, every service that references it could, in theory, reflect that change—breaking the cycle of manually updating dozens of separate platforms. This creates a "single source of truth" model for digital identity.

Top Questions & Answers Regarding the human.json Protocol

Is this just another standard that will be ignored by big tech companies?
Most likely, in the short term. Facebook or Google have little incentive to adopt a standard that decentralizes identity away from their walled gardens. The initial value proposition is for the independent web, the fediverse (Mastodon, etc.), and developer tools. Its success path mirrors that of RSS: niche adoption leading to undeniable utility, potentially forcing larger players to eventually support it, if only for interoperability with the broader ecosystem.
How does human.json handle privacy and sensitive information?
The protocol, in its base form, is for public identity. It's not designed to hold private data. The specification suggests fields are optional, and users only publish what they wish to be publicly discoverable. For private data exchange, it would need to be part of a larger system with authentication. The philosophy is "publish what you own, on your terms."
What's stopping someone from creating a fake human.json file about me?
This is a critical challenge for any decentralized identity system. The protocol relies on the authority of the domain. The canonical `human.json` file is the one at the root of your verified domain. Ownership/control of the domain is the primary proof of authenticity. For stronger verification, the spec mentions the potential for linking to cryptographic keys or other verifiable credentials, moving towards a true self-sovereign identity model.
What practical tools currently support human.json?
As an emerging standard, the ecosystem is nascent. Some personal site generators have begun to include plugins or templates for auto-generating the file. The most immediate use is for developers and technically-minded individuals to manually create the file, establishing the foundational layer. Broader adoption will require the development of parsers for search engines, social readers, and contact management apps.

The Road Ahead: Challenges and Transformative Potential

The fate of `human.json` hinges on a classic network effect problem. Its value is minimal if only a handful of tech enthusiasts use it, but grows exponentially as adoption spreads. The challenge is catalyzing that initial adoption.

Potential Catalysts:

  • IndieWeb Integration: Widespread adoption by IndieWeb tools and community members could establish it as a de facto standard for personal sites.
  • Search Engine Recognition: If a major search engine like Google or DuckDuckGo began parsing `human.json` to enhance personal site rich results, it would provide a powerful incentive for creation.
  • Fediverse Adoption: Mastodon instances or other ActivityPub platforms could use `human.json` from a user's profile link to auto-populate profile information, creating a seamless link between the open social web and personal sites.

Beyond Identity: The Ripple Effects

If successful, `human.json` could have ripple effects beyond simple profile data. It could evolve to include:

  • Preference Signals: Declaring your preferred pronouns, communication styles, or accessibility needs in a machine-readable way.
  • Creative Licenses: Attaching default licenses for your content (CC BY-SA, etc.) directly to your identity.
  • Skill & Endorsement Frameworks: A simple, self-declared skills matrix that complements, rather than replaces, platform-specific systems like LinkedIn's.

In essence, `human.json` is not merely a technical specification. It is a manifesto in code—a statement that our digital selves should be as portable, editable, and owned as a text file on our own website. In an age of increasing digital centralization and abstraction, it offers a path back to a web that is fundamentally more human. Its success is far from guaranteed, but its vision is precisely the kind of foundational thinking the open web desperately needs.