Build a NepTunes widget.
Widgets are just HTML, CSS and JavaScript in a .nepget bundle. Read live track data, draw whatever you like, and control playback through a small JavaScript API.
Introduction
What a NepTunes web widget is, how the .nepget bundle works, and where widgets live.
Quick start
Build a minimal NepTunes widget in about five minutes.
manifest.json reference
Every field in a widget's manifest.json, with types and defaults.
JavaScript API
The window.NepTunes object — state, actions, events, settings and artwork.
Settings schema
Let users configure your widget with checkboxes, sliders, pickers and more.
Permissions
Declare only the capabilities your widget actually uses.
Debugging
Widgets can't be inspected in place — develop them in a browser, then read the host's log to find out why one isn't showing up.
Publishing guidelines
The review bar for getting your widget into the NepTunes gallery.
Updates & signing
How a .nepget bundle is signed with bundle.sig, what NepTunes verifies before installing it, and how ids, rotation and updates work.
Build with an AI assistant
Connect Claude, Cursor, Codex or OpenCode to the NepTunes widget docs via MCP.
Security & the sandbox
What a widget can and cannot reach, and how to build inside those limits.