AIMP Cloud Storage Not Connecting: How to Fix It

When AIMP cloud storage is not connecting, the fault usually falls into one of five categories: the cloud account authorization has expired, the service requires a WebDAV connection, the saved server address or credentials are incorrect, the device or network is blocking access, or AIMP can reach the storage but cannot open the selected folder or audio file. The safest approach is to test one known-good file and change one setting at a time. That method helps you identify the real cause without deleting playlists, rebuilding your library, or reinstalling AIMP unnecessarily.

AIMP handles cloud access differently across platforms. On Windows, supported cloud services and custom WebDAV connections may be available through AIMP's cloud integration. On Android, cloud playback depends primarily on a provider that exposes WebDAV, while network storage can also involve protocols such as Samba or FTP. A cloud provider's normal website login is not automatically the same thing as a working WebDAV login. Keep that distinction in mind as you work through the checks below.

1. Confirm the Symptom With a Small Safe Test

Begin by reducing the problem to one account, one folder, and one small audio file. Do not start with a large playlist, a smart playlist, a complete music-library scan, or a high-resolution album. Those introduce additional variables and make it harder to tell whether the connection itself is failing.

1.1 Test One Small Supported Audio File

Place a short MP3 or another format that you already know AIMP can play in a simple folder near the top level of the cloud account. Give the file and folder ordinary names without unusual symbols. Then browse to that folder from AIMP and try to play the file directly.

The test can produce three useful outcomes:

• If AIMP cannot display the account or folder, investigate authorization, WebDAV settings, credentials, permissions, and network access.
• If AIMP displays the file but cannot begin playback, investigate file access, downloading or streaming behavior, file format support, and the audio output path.
• If the test file plays, the cloud connection is working. Stop changing account and network settings and focus on the original folder, playlist entry, or source file.

Success means the test track begins playing, its duration appears correctly, and playback continues rather than stopping after a few seconds. Once that happens, do not keep resetting authorization or modifying firewall rules. Move on to comparing the working file with the content that fails.

1.2 Compare Direct Browsing With the Existing Playlist

A saved playlist can retain an outdated cloud path after a file is renamed, moved, or re-shared. Browse to the test file through AIMP's cloud or file interface instead of selecting an old playlist entry. If direct browsing works but the playlist item fails, remove only the broken entry and add the file again from its current location.

If the same track is also listed in the music library, verify the library entry points to the current cloud location rather than an old local cache or obsolete URL. There is no reason to delete the entire playlist or library when one stale reference is the cause.

2. Check AIMP's Cloud Connection and Playback State

2.1 Reauthorize the Cloud Account on Windows

A cloud account can remain visible in AIMP even after its authorization token has expired or been revoked. This commonly follows a password change, a security review, removal of connected applications, or a change to multi-factor authentication.

Open AIMP's cloud storage area and try to refresh or browse the affected account. If AIMP requests authorization, complete the provider's official sign-in process. If it repeatedly returns to the login screen, remove that cloud connection from AIMP and add it again. Remove only the account connection, not your local music files or unrelated playlists.

During authorization, approve the file-access permission required for AIMP to list and play audio stored in the account. If access was previously denied, the account may appear connected while its folders remain empty or unavailable.

Success means AIMP can refresh the account, list its folders, and open the test file. At that point, stop reconnecting the account. Repeatedly revoking a successful authorization can create more confusion.

2.2 Verify Whether the Provider Requires WebDAV

Not every cloud provider has a dedicated AIMP connection. Some services must be added as custom WebDAV storage. On Android, the cloud provider must offer usable WebDAV access for AIMP's cloud-storage feature. A normal browser URL, sharing page, or mobile-app address is usually not a WebDAV endpoint.

Check the cloud provider's current documentation for its exact WebDAV server address. Enter the complete address, including the correct secure protocol and any required path. Prefer HTTPS whenever the provider supports it. Do not guess the endpoint by adding “webdav” to the provider's public website address.

Some services require an app-specific password instead of the account's ordinary password, especially when multi-factor authentication is enabled. Others may have discontinued WebDAV or limited it to particular plans. If the provider does not support WebDAV and has no dedicated AIMP integration on your platform, changing AIMP's audio settings will not create that support.

Success means AIMP accepts the connection and displays the expected remote folders. If authentication succeeds but only one folder is missing, investigate that folder's permissions rather than changing the server address again.

2.3 Replace Expired Passwords, Tokens, and App Passwords

Re-enter the credentials if the password recently changed. For WebDAV, confirm whether the username should be an email address, account name, or provider-generated identifier. Password managers can also paste an old credential or include a trailing space, so enter the value carefully.

If the service uses an app password, create a new one through the provider's official security settings and save it in AIMP. Do not turn off multi-factor authentication merely to make the connection easier. A fresh app password is the safer solution when supported.

A successful fix changes the behavior immediately: folders load or the test track starts. If the credentials are accepted but playback still fails, stop changing passwords and proceed to folder and file checks.

2.4 Check the Relevant Plugin on Windows

AIMP's Windows cloud functionality depends on its cloud integration component. Open AIMP's plugin settings and confirm the relevant cloud plugin is installed and enabled. If the account area disappeared after a settings change or update, an inactive plugin is more likely than an audio codec problem.

Temporarily return to AIMP's standard skin if a custom skin hides a panel, command, or status message you need for troubleshooting. A skin can affect access to controls, but it normally does not determine whether the provider accepts a password. If the same failure occurs with the standard interface, stop changing skins.

Avoid installing unrelated third-party plugins as a speculative fix. Add-ons that do not provide the required cloud protocol cannot repair an expired token or an incorrect WebDAV address.

2.5 Separate Connection Problems From Output Problems

If AIMP lists cloud folders and reads the track's duration but produces no sound, the cloud connection may already be working. Test a local track with the same AIMP session and output device. If local and cloud tracks are both silent, check AIMP's selected output method, Windows volume mixer, default playback device, exclusive device use, Bluetooth output, or Android media volume.

If local audio plays and the cloud track never starts loading, return to network, credentials, permissions, and file availability. Do not change output devices when AIMP cannot even list the remote folder because output settings cannot fix account authorization.

3. Check Network, Permissions, and Remote Storage Access

3.1 Test the Network Without Weakening Security

Confirm the device can open the cloud provider's official website or app on the same connection. If possible, briefly compare Wi-Fi with another trusted network or mobile data. A successful test on one network but not another points to DNS filtering, a proxy, VPN routing, captive-portal login, router restrictions, or organizational network policy.

On Windows, allow AIMP through the firewall for the appropriate trusted network profile if a block is recorded. If third-party security software reports that it blocked AIMP, create a narrow application rule rather than disabling protection permanently. On a managed work or school network, ask the administrator whether WebDAV or the provider's domains are restricted.

Success means the account refreshes and the small test file plays on the original network after the appropriate rule or login is corrected. Once it works, remove any temporary diagnostic network changes you no longer need.

3.2 Verify Folder and Sharing Permissions

Being able to sign in does not guarantee that the account can read every folder. Shared folders may have expired invitations, changed ownership, restricted external access, or permissions that allow viewing through a browser but behave differently through WebDAV or an application interface.

Create or select a folder owned directly by the account and place the test file there. If that works while a shared folder fails, restore read access to the shared folder or copy the required music to a location the account can read reliably. For a self-hosted WebDAV server or NAS, confirm the user has permission to list the directory and read the file itself.

Success means the problem follows the folder rather than the account. Stop resetting the whole cloud connection and correct only the affected folder's access.

3.3 Grant Android Storage and Network Permissions

On Android, open the system settings for AIMP and review the permissions relevant to music, audio files, photos or artwork, and local network access where available. Storage permission affects local files and cached or downloaded content. Local network permission may matter when AIMP connects to WebDAV or a NAS hosted inside your home network.

If AIMP uses Android's system file-access dialog, grant access to the specific folder or storage location that contains the music. Moving files to another folder can invalidate an earlier folder grant. Select the new location through AIMP rather than assuming the old permission follows the files.

Success means AIMP can reopen the folder after the app is closed and launched again. If WebDAV authentication fails before any folders appear, storage permission alone is unlikely to be the cause.

3.4 Remove Battery and Data Restrictions That Interrupt Streaming

Some Android devices restrict background network activity aggressively. If a cloud track starts but stops when the screen turns off, review battery optimization, background activity, background data, and data-saver settings for AIMP. Permit the level of background operation needed for uninterrupted playback, especially when streaming long tracks.

Also check whether a VPN, private DNS service, or mobile data limit affects the cloud provider. Make one temporary comparison with the feature paused, then restore it and configure a targeted exception if necessary. Do not leave security or privacy tools disabled merely because the test succeeded.

Success means playback continues with the screen off and survives normal track changes. Once continuous playback works, avoid changing account credentials because authorization was not the problem.

3.5 Confirm the Source File Is Readable

A file can have a familiar extension while still being incomplete, corrupted, encrypted, protected by unsupported DRM, or encoded in a way the current player cannot decode. Download the failing file through the provider's official app or website and test that local copy in AIMP. Also test a different small file from the same remote folder.

• If every file in the folder fails, suspect folder access, connection configuration, or the server.
• If one file fails while others play, suspect that file's content or upload quality.
• If the downloaded local copy also fails, cloud connectivity is not the primary issue.
• If the local copy plays but remote playback fails, investigate streaming support, server responses, and network stability.

Do not install a random codec pack. Use a valid source file in a format AIMP supports, or convert an unprotected file you own with a reputable tool when appropriate.

4. Use AIMP's Built-In Information to Narrow the Cause

4.1 Inspect File Information and the Remote Path

Open the affected track's file information or properties in AIMP. Compare its location with the working test file. An old URL, renamed directory, missing filename, or unexpected local cache path can explain why a playlist item fails even though the account connects.

Metadata and artwork failures should also be separated from playback failures. If the audio plays but cover art or tags are absent, the connection is functioning. Check whether artwork is embedded in the file, stored as a separate image in a readable folder, or referenced by an unavailable URL. Use AIMP's tag editor only on a local writable copy when the cloud connection is read-only.

4.2 Refresh the Playlist or Rescan the Music Library

After moving files or restoring a cloud account, remove a broken playlist entry and add the track again by browsing the active connection. For library-based views, run the narrowest available rescan that covers the affected source. Avoid deleting the entire database as a first response.

Success means the newly added entry plays while the obsolete entry does not. That confirms stale playlist or library data rather than a continuing cloud failure.

4.3 Treat Radio, Podcast, and Cloud URLs Separately

An internet radio station, podcast episode, public share link, and WebDAV file are not interchangeable. A web page that contains a play button is not necessarily a direct audio stream. Similarly, a cloud sharing link may require cookies, redirects, or a browser session and therefore may not work as a direct playlist URL.

If only one radio or podcast URL fails, test another known working source before altering the cloud account. If cloud browsing works but a pasted share link fails, add the storage through its supported cloud or WebDAV method instead of treating the share page as an audio file.

4.4 Keep Converter and Playback Tests Separate

AIMP's audio converter may need to read the complete source and write to a permitted destination. A cloud track that streams successfully is not proof that it can be converted directly from the remote source. Download a legal, unprotected copy to a writable local folder and test conversion there.

If local conversion works, the encoder and output settings are functional. The remaining issue concerns remote-source access, temporary storage, or the cloud server's ability to provide the complete file. Do not keep changing encoder options when AIMP cannot retrieve the source data.

5. Run a Clean Temporary Test Before Reinstalling

Before reinstalling AIMP, create a controlled test that leaves your normal playlists and library intact. Close unnecessary add-ons, switch temporarily to the standard skin, create a new empty playlist, and add only the small cloud test file from a freshly authorized connection.

1. Record the current server address and relevant settings without exposing the password.
2. Create a new playlist rather than editing an important one.
3. Reconnect one account or WebDAV source.
4. Browse directly to one small file.
5. Play it without enabling extra processing or unrelated plugins.
6. Add a second file from the previously failing folder.

If the clean playlist works, compare it with the original playlist, library entry, skin, or plugin setup. If it still fails, collect the exact error message, AIMP platform, operating system, connection type, server address format with private details removed, and the step at which it fails. That information is more useful for support than a general report that AIMP is not working.

Reinstallation should be a late step because it may leave the real cause untouched. Cloud passwords, revoked tokens, server permissions, Android battery restrictions, and network blocks exist outside AIMP's program files. If you do reinstall, preserve playlists and settings first, and obtain the installer from AIMP's official download page.

6. Quick Fix Checklist

• Test one small, known-good audio file in a simple cloud folder.
• Browse directly to the file instead of using an old playlist entry.
• Reauthorize the cloud account after password or security changes.
• Use an app-specific password when the provider requires one.
• Confirm the provider supports AIMP directly or supplies WebDAV access.
• Copy the exact WebDAV endpoint from the provider's current documentation.
• Verify the username format, password, secure protocol, and remote path.
• Confirm the account can list the folder and read the file.
• Compare a private account-owned folder with the failing shared folder.
• Test another trusted network to identify local filtering or routing problems.
• Allow AIMP through the firewall narrowly instead of disabling security.
• Grant relevant Android storage and local-network permissions.
• Remove battery or data restrictions if playback stops in the background.
• Test the downloaded file locally to rule out corruption or unsupported content.
• Enable the relevant Windows cloud plugin and temporarily use the standard skin.
• Refresh only the affected playlist entry or library source.
• Stop changing settings as soon as the account lists folders and the test file plays.

7. Frequently Asked Questions

7.1 Why does AIMP reject my normal cloud password?

The provider may require an app-specific password for WebDAV or third-party applications, particularly when multi-factor authentication is enabled. The saved password may also have expired after an account security change. Confirm the provider's current requirements and create a new app password if supported.

7.2 Can I paste a cloud sharing link into AIMP?

Only if the link resolves to a usable direct audio resource supported by AIMP. Most sharing links open web pages and require browser sessions. For reliable access, add the account through AIMP's supported cloud integration or use the provider's documented WebDAV endpoint.

7.3 Why does cloud storage work on Windows but not Android?

The two editions do not necessarily use identical cloud connection methods. A provider with a dedicated Windows integration may still require WebDAV on Android. Android can also impose storage, local-network, background-data, and battery restrictions that do not apply to Windows.

7.4 Why can AIMP see my folders but not play a track?

Folder listing proves that some authentication and network communication succeeded, but it does not prove the account can read the file data. Check file-level permissions, shared-folder access, source-file integrity, format support, and whether the server permits streaming or complete-file retrieval. Test a small file owned directly by the account.

7.5 Should I reinstall AIMP when cloud storage stops connecting?

Usually not as the first step. Reauthorize the account, verify the WebDAV endpoint, replace expired credentials, test the network, check permissions, and try a clean playlist first. Reinstallation is more appropriate when AIMP's cloud component is missing or damaged and the same account works correctly elsewhere.

7.6 How do I know the AIMP cloud storage not connecting fix worked?

The account should refresh without repeated login prompts, the expected folder should open, and a small test file should begin and continue playback. If all three occur, stop changing connection settings. Any remaining problem is more likely tied to a particular playlist entry, folder permission, source file, output device, or background-playback restriction.