Step-by-Step Fix
1. Check Midjourney's Status
Before troubleshooting the app itself, confirm there is no active outage at status.midjourney.com. Desktop app login failures during a service incident will not be fixed by local changes.
2. Update the Desktop App
Running an outdated desktop app version is a common cause of login failures after Midjourney updates their API.
- Open the Midjourney desktop app
- Look for Help → Check for Updates or an equivalent menu option
- If an update is available, install it
- Restart the app and attempt login
If no in-app update is available, download the latest version from midjourney.com and reinstall.
3. Sign Out and Sign Back In
A stale or corrupted authentication token in the app causes persistent login loops.
- In the desktop app, find the account/profile menu
- Click Sign Out
- Wait for the sign-out to complete
- Click Sign In and complete the Discord or Google authorization
- Check if login succeeds
4. Clear the App Cache
If signing out and back in does not help, clear the app's local cache:
On Mac:
- Quit the Midjourney app completely
- Open Finder → Go → Go to Folder (Cmd+Shift+G)
- Enter:
~/Library/Application Support/Midjourney/ - Delete or move the cache folder contents to Trash
- Reopen the app and sign in fresh
On Windows:
- Close the Midjourney app completely
- Press Windows+R, type
%APPDATA%, press Enter - Find and open the Midjourney folder
- Delete the Cache folder or its contents
- Reopen the app and sign in fresh
5. Check Your Firewall and Antivirus
Desktop apps need to make outbound network connections for authentication. If your firewall or antivirus software is blocking the Midjourney app's network requests:
- Temporarily disable your firewall/antivirus
- Try logging in
- If it works, add the Midjourney app as a trusted exception to your security software
- Re-enable your firewall/antivirus
6. Try the Web Interface as a Fallback
If the desktop app continues to fail:
- Open your browser and go to midjourney.com
- Sign in with Discord or Google
- You have full access to all Midjourney features through the browser
The web interface is identical in functionality to the desktop app for most operations.
7. Use Discord Desktop App as an Alternative
- Download and install Discord from discord.com if not already installed
- Log in to your Discord account
- Join the Midjourney server (discord.gg/midjourney)
- Use the /imagine command in any bot channel
The Discord desktop app is the original Midjourney access method and is fully supported.
8. Reinstall the Desktop App
If all else fails:
- Uninstall the Midjourney desktop app
- Delete remaining app data folders (see step 4 for locations)
- Download the latest installer from midjourney.com
- Install fresh and sign in
Why This Happens
The Midjourney desktop app stores authentication tokens and cache data locally. These can become stale when the app is not updated to match the current API version, when the OAuth token expires without a clean renewal, or when the local cache becomes corrupted. Unlike the browser, where clearing cache is a standard and well-known procedure, desktop app cache management is less visible, leading users to focus on account-level issues rather than local app issues.
Common Mistakes to Avoid
- Not updating the app before troubleshooting — An outdated app version is the easiest-to-fix cause of desktop login failures.
- Assuming the problem is your account — If the web interface works, the issue is the desktop app's local state, not your account.
- Reinstalling without clearing the cache first — Reinstalling the app over an existing installation sometimes preserves the corrupted cache. Delete the cache folder after uninstalling.
- Skipping the fallback options — The web interface and Discord desktop app are fully functional alternatives that allow you to keep working while troubleshooting the standalone app.
- Not adding the app to your firewall's allow list — Security software on corporate or personal computers frequently blocks desktop apps from making OAuth callbacks.
Related Issues
- Midjourney login not working on mobile
- Midjourney Discord authorization issues
- Midjourney can't log in
- Midjourney login not working
Q: Is there a way to keep the Midjourney desktop app logged in without repeated sign-ins? The desktop app stores a session token that typically stays valid for 30 days. If you are being asked to sign in more frequently, the token may be expiring prematurely due to a corrupted cache or an app update invalidating old tokens. After clearing the cache folder (see step 4 above) and signing back in, your session should remain stable. Avoid clearing the app's storage aggressively, as this also removes the session token. If your antivirus software quarantines files in the app's storage directory, it may be removing the token unintentionally.
Q: Does the Midjourney desktop app work on Linux? Midjourney does not officially release a Linux desktop app. On Linux, the correct access methods are the Midjourney web interface at midjourney.com (works in Chrome and Firefox on Linux) or the Discord desktop app on Linux, which supports the Midjourney bot via the /imagine command. If you are on Linux and experiencing issues, use the browser-based method at midjourney.com as your primary interface rather than waiting for a desktop app that does not exist for your platform.
Q: What is the difference between the Midjourney desktop app and the Discord desktop app for Midjourney use? The Midjourney standalone desktop app is a purpose-built application that connects directly to midjourney.com and provides the web-style gallery and generation interface in a desktop wrapper. The Discord desktop app runs the Discord client, and within it, you join the Midjourney server (or a private server with the bot) and use slash commands like /imagine. Both access the same Midjourney backend and subscription. The Discord app shows community channels and social features alongside generation; the Midjourney standalone app is more focused on your personal gallery and prompts.
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.