porndb.me launches a new version: metadata matching and account migration
porndb.me has released its rebuilt app. What changes for metadata, indexer connections, downloads, existing accounts and integrations using the old API.
porndb.me released its new version on October 16, 2026. According to the relaunch announcement, a newly built application at app2.porndb.me replaces the beta that had been running since 2019. PornDB remains focused on metadata for adult Usenet releases and does not host video files.
For existing users, the change reaches beyond the interface: release matching, personal indexer connections and download access have been reorganised. The previous API has been shut down.
Connecting metadata with releases
The new interface centres on catalogue entries with preview images and metadata. Performer names, aliases, sites and networks come from prdb.net. PornDB collects entries from supported NZB indexers in the background and matches them to that catalogue.
The operatorâs technical explanation describes a sequence of matching rules, including release names confirmed by PreDB and combinations of site and date. Entries without an unambiguous match stay unmatched. A separate release search includes these entries, but covers only data already collected, rather than an indexerâs entire history.
Multiple releases associated with the same catalogue entry remain individually visible, each with its indexer, size, resolution and date. That separation is useful when comparing sources: sharing a metadata record does not erase the differences between releases.
Personal indexers and data collected on the server
NZBPorn is integrated. Other supported indexers, including NZBFinder and DrunkenSlug, can use personal API keys. A test mode without a key allows inspection of the listed entries, but does not enable downloads from that indexer.
According to the operator, search and filtering use data previously collected on PornDBâs servers. Here, âlocalâ means within PornDBâs infrastructure. Individual searches therefore do not trigger live requests to an indexer or the prdb.net API. This reduces the browsing requests shared with those services, but does not establish what PornDB itself logs.
The operator says personal indexer keys are stored encrypted and used in direct download links opened by the browser at the relevant indexer. Browsing and search are free; NZB downloads require an active prdb.net membership. Downloads from external indexers also remain subject to the terms of the userâs account there.
Moving existing accounts and integrations
The migration documentation sets out the main boundaries:
- Deadline: Migration is available until October 1, 2027, at 00:00 UTC.
- Account and indexer keys: The old password proves account ownership; saved indexer keys can then be explicitly selected for transfer.
- Excluded: Favourites, playlists, filters, history, and previous plans and roles do not transfer.
- API and RSS: The old interfaces have been shut down. The operator says
api.porndb.mereturns410 Gone; there is currently no new public API.
That last point matters for an existing self-hosting setup: migrating an account does not restore old automation. Scripts and clients previously connected to the PornDB API or its RSS feeds need their integrations reviewed.
As of October 17, 2026. Based on the linked operator documentation; no signed-in account test was performed. Disclosure: prdb.net and nzbporn.org sponsor nzb.is.