Organizing a 115 Cloud Drive Media Library
Files on 115 often carry messy release-group names that players cannot identify. This guide shows how to sign in with the official 115 open platform OAuth login, scrape TMDB and batch rename so cloud files feed straight into your media wall.
Last updated:
Why 115 files must be renamed
Media shared on cloud drives usually keeps the release-group filename, with title, year, resolution, codec and tracker tag strung together on one line. Handed that, a player either shows an unknown title or matches something completely unrelated — hence the mess on your media wall.
115's built-in rename only does rule-based find and replace. It cannot work out which show and which episode a messy filename refers to. That is the part AI renaming solves.
Connecting with the official 115 open platform OAuth
VRenamer uses 115's official open platform (Open API) and signs in to your own account through OAuth authorization code flow — there is no third-party WebDAV bridge. File listing and renaming both happen over official endpoints, and nothing is downloaded locally.
- Add a 115 Cloud file source in VRenamer and tap Add
- In-app, the official 115 authorization page opens; sign in and approve access
- You are returned to the app automatically and tokens are stored locally; they refresh silently when they expire — no repeated logins
- Browse the drive and pick the media folders interactively
If a token expires or access is revoked, the app asks you to re-authorize. Tap Re-authorize on the edited file source; nothing else in the configuration is affected.
The workflow
- Scan the selected folders; VRenamer lists candidates grouped by directory
- AI matches TMDB using both filename and folder structure, proposing title, year, season and episode
- Fix wrong matches manually, or restructure into show (year) folders and scan again
- Run the batch rename; subtitles are renamed with their videos
- Enable bilingual naming if you want outputs like Localized.English.Name.S01E01
After organizing
With clean naming, 115 files can be mounted into Emby, Plex, Jellyfin or Infuse via official WebDAV or similar, building a media wall without a local copy. VRenamer itself talks to the drive over the official open platform API — mounting it in a player is a separate path.
FAQ
Does 115 use WebDAV or the official API?
The official open platform OAuth API. You sign in with your own 115 account, so all operations — renaming included — go through official endpoints with full capability. There is no WebDAV bridging.
Will renaming download the files?
No. Renaming changes names on the drive side. File content never passes through your device and no extra traffic is used.
What if the 115 authorization expires?
Tap Re-authorize on the file source and go through the official flow once more. Tokens refresh automatically while valid, so normal use needs no repeated logins.