Cross Domain · protocol · IETF JMAP Working Group

JMAP FileNode (JMAP File Storage Extension)

The IETF JMAP working group’s file-system extension — draft-ietf-jmap-filenode, at revision 14 in May 2026 and headed for Proposed Standard — which exposes JMAP blobs as a tree of files and folders with the metadata remote file-system protocols provide. Its stated aim is to replace WebDAV for files the way JMAP’s mail, calendar and contacts profiles replace IMAP, CalDAV and CardDAV. Metadata and bytes are separate objects, and change tracking comes free from the base protocol.

datatracker.ietf.org/doc/draft-...The standard

IETF JMAP Working GroupGoverning body

2024First published

draft-ietf-jmap-filenode-14 (15 May 2...Current version

0providers in the catalog

Also known as draft-ietf-jmap-filenode, JMAP File Storage, JMAP Files.

Providers that carry JMAP FileNode 0

No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements JMAP FileNode and says so in its APIs.json profile appears here on the next build. Add or correct a listing.

Read from the API Evangelist standards directory, facts verified 2026-10-07. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.