No Login Data Private Local Save

Content Indexing API Test - Online Add to Device's Media Feed

Developer Tools PWA API Content Indexing PWA test
38
0
0
0

Content Indexing API Test – Add to Device’s Media Feed

Quickly test if your content can be indexed by the browser’s Content Index and appear in the device’s media feed or downloads surface.

Browser Support

Checking...

Detecting
Add Test Content
Please enter a valid URL (HTTPS required).
Title is required.
Icon preview
Recommended 192x192 or larger PNG.
ID will be auto‑generated based on URL.
How it works

This tool calls navigator.contentIndexing.add() with the data you provide. If the API is supported, the browser may index your content and show it in:

  • Chrome’s Downloads / media notifications
  • Android’s media controls
  • System‑level sharing surfaces

A registered Service Worker is recommended for offline content playback.

Sample code 
const item = {
  id: 'post-1',
  title: 'My Article',
  description: '...',
  url: 'https://...',
  icons: [{
    src: 'https://.../icon.png',
    sizes: '192x192',
    type: 'image/png'
  }],
  category: 'article'
};
try {
  await navigator.contentIndexing.add(item);
} catch (e) {
  console.error(e);
}

Frequently Asked Questions

A web API that lets progressive web apps tell the browser which content is available for offline use. The browser can then surface that content in its UI (e.g., Downloads, media controls) so users can easily find and revisit it.

Currently supported in Chromium-based browsers (Chrome 84+, Edge 84+, Opera 70+). Firefox and Safari have not yet implemented it. This page performs a live check for you.

Technically, navigator.contentIndexing.add() can be called without a Service Worker, but for the indexed content to be useful (offline playback), you should register a fetch handler in a Service Worker. Without one, the browser may still index the URL, but opening it might fail when offline.

You must serve your site over HTTPS. Use localhost (which is considered secure) or a tool like ngrok. Also enable the #content-indexing flag in chrome://flags if it's not already on.

The API requires a user gesture (e.g., a click) and must run in a secure context. If your site isn't installed as a PWA or if the feature is blocked by browser settings, you may see this error. Our tool triggers the call directly from a button click.

Yes. Use navigator.contentIndexing.delete(id) to remove an item by its ID. There is no direct update method — delete and re-add with the same ID to update.

You can specify any URL, but categories such as article, video, audio, or homepage help the browser present the item properly. There is no strict content‑type enforcement.
🔧 Related Tools