Complete guide — how to use Midjourney, fix common errors, manage billing, and get the most out of every feature.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney enforces a concurrency limit of 3 simultaneous Fast mode jobs on Standard plans and up to 12 on Mega — when you hit the rate limit, wait 60 seconds before retrying, reduce parallel requests, and switch to Relax mode if available on your plan to continue generating without consuming GPU hours.
Your Midjourney billing history is accessible at midjourney.com/account under the Billing section — each subscription charge and any additional Fast hour purchases appear there with dates and amounts. If a charge appears on your bank statement but not in Midjourney's history, the payment likely failed mid-processing and will reverse within 3 to 5 business days.
Midjourney offers 4 billing plans: Basic ($10/mo, ~200 images), Standard ($30/mo, 15 Fast GPU hours + unlimited Relax), Pro ($60/mo, 30 Fast GPU hours + 12 concurrent jobs), and Mega ($120/mo, 60 Fast GPU hours). Manage your plan at midjourney.com/account — changes take effect immediately or at the next billing cycle depending on whether you upgrade or downgrade.
Midjourney offers 4 plans: Basic ($10/mo, 200 images), Standard ($30/mo, unlimited relaxed + 15 GPU hrs fast), Pro ($60/mo, 30 GPU hrs fast), and Mega ($120/mo, 60 GPU hrs fast). To change your plan, go to midjourney.com → Manage Subscription, and select Upgrade or Downgrade. Upgrades take effect immediately with prorated credit; downgrades take effect at the start of your next billing cycle, so you will not lose access mid-cycle.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Contact Midjourney billing support through docs.midjourney.com (submit a request) or the #billing-support channel in the official Midjourney Discord server — have your registered email address, transaction ID from your Stripe receipt, and a description of the issue ready. Most billing issues resolve within 1 to 3 business days.
The Midjourney bot disappears from a Discord channel most often because the bot was not explicitly added to that channel, channel permissions do not allow the bot to see or post there, or the bot was accidentally kicked from the server. To fix it, go to your Discord server settings, check the Midjourney Bot's role permissions, and if needed, re-invite the bot via the official Midjourney website.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Over 90% of Midjourney login failures are caused by browser issues, expired sessions, or OAuth token errors — clear your cookies for midjourney.com, open an incognito window, and try logging in again. If you use Google or Discord to sign in, revoke and re-authorize the connection. Check status.midjourney.com for any active outages before spending time troubleshooting locally.
Fix Midjourney billing issues by confirming the purchase channel, verifying the card/bank auth, refreshing your subscription status (sign out/in), and checking for pending vs posted charges. If access is still locked, contact support with the receipt/transaction ID.
Midjourney's automated content moderation uses a keyword and context filter that blocks prompts containing terms related to violence, nudity, or specific real-world figures — removing or rephrasing just the flagged term usually unblocks the generation. Midjourney's filter is not perfect and sometimes flags benign words; try rephrasing with synonyms, adding descriptive art-style context, or breaking complex prompts into simpler components.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Midjourney's 'creation failed: internal server error' means the job failed on Midjourney's GPU servers — this error occurs on the server side, not your device. Wait 2 to 5 minutes and retry your prompt, check status.midjourney.com for outages, and simplify your prompt if failures persist. Most internal server errors resolve within a single retry.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Fix Midjourney errors by hard-reloading, clearing cache, reducing request size, and testing another browser/network. Capture the exact error text + timestamp for support if it persists.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
If Midjourney can’t download an image: try a direct browser open, disable download/privacy extensions, switch networks (hotspot), and retry from a fresh session. If it’s widespread, wait for CDN/outage recovery.
The 'failed to download image' error in Midjourney occurs when the generated image cannot be delivered from Midjourney's CDN to your client — refresh the page and click the image again, try right-clicking and selecting 'Open image in new tab,' or use the web gallery at midjourney.com to access the generated image directly.
Midjourney's 'error loading image' typically means a reference image URL is invalid, blocked, or too large — use a direct image URL (ending in .jpg, .png, or .webp) rather than a webpage URL, ensure the image is publicly accessible without login, and keep uploaded reference images under 25MB. If the error appears on a generated image, refresh and try again.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
The 'your unique trace' error in Midjourney is a job tracking identifier included in error messages to help support diagnose failures — copy the trace ID from the error message, note the time it occurred, then retry your prompt. If the error repeats, submit the trace ID to Midjourney support at docs.midjourney.com so they can investigate the server-side failure.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Midjourney bug reports submitted through their official channels (Discord #bug-reports channel or docs.midjourney.com support) are most effective when they include: the exact error message or behavior, the full prompt used, your plan tier (Basic/Standard/Pro/Mega), the specific channel or interface (Discord vs. web), timestamps, and screenshots or screen recordings. Reports without reproduction steps are rarely actionable.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Midjourney Fast mode uses your monthly GPU hours (15 hrs on Standard, 30 hrs on Pro, 60 hrs on Mega) and stops being available when those hours run out; Relax mode is unlimited but only available on Standard and higher plans. If Fast mode is not working, check your remaining GPU hours with the /info command in Discord. If Relax mode is unavailable, you may be on the Basic plan ($10/mo), which does not include Relax mode.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Midjourney Basic plan includes approximately 200 image generations per month (roughly 6–7 per day); Standard plan provides 15 hours of GPU time per month with unlimited relaxed generations. When you hit your daily or monthly cap, wait for the reset window or upgrade your plan to continue generating.
Midjourney limits are monthly, not daily — the Basic plan gives 200 image generations per month, Standard gives 15 fast GPU hours plus unlimited Relax mode, Pro gives 30 fast GPU hours, and Mega gives 60 fast GPU hours. If you hit the limit, you can switch to Relax mode (Standard and above), buy additional fast GPU hours (~$4/hr) in the Manage Subscription portal, or wait until your next billing cycle. Use /info in Discord to check your exact remaining balance.
Midjourney temporary restrictions are triggered by behaviors that resemble automated abuse: submitting dozens of jobs in rapid succession, repeatedly attempting blocked content, logging in from multiple unusual IP addresses, or making excessive API calls. Restrictions typically last 24 to 72 hours and lift automatically. To avoid them, pace your generations, use one stable network connection, and avoid retrying content-moderation-blocked prompts more than 2-3 times.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Midjourney desktop app login failures are most often caused by a corrupted local app cache, an outdated app version, or an expired Discord OAuth token — update the app to the latest version, clear the app's cache folder, and sign out then back in. If the desktop app continues to fail, use the web interface at midjourney.com or access Midjourney through the Discord desktop app as a working alternative.
Midjourney mobile login failures on iOS or Android are most often caused by an outdated app version, the phone's built-in browser blocking the OAuth redirect, or a system-level restriction on pop-ups and redirects. Update the app to the latest version from the App Store or Google Play, clear the app's cache in your phone's settings, and ensure the in-app browser is not blocked from completing the Discord or Google authorization.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Midjourney login stops working most often due to expired Discord OAuth tokens, corrupted browser cookies, or a network blocking the authentication redirect — clear your cookies for midjourney.com and discord.com, disable browser extensions, and attempt login from an incognito window. If you recently changed your Discord password, you must re-authorize the Midjourney connection. Check status.midjourney.com for outages before troubleshooting.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
If the Midjourney login page is not loading, shows a blank screen, or keeps looping, the fix is almost always one of three things: clear your browser cookies and cache for midjourney.com, disable extensions that block scripts, or switch to a different browser. The login page loads from midjourney.com and requires JavaScript and Discord/Google OAuth to complete — both must be unblocked.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Fix Midjourney login problems by clearing site cookies, disabling extensions/VPN, completing OAuth re‑authorization (Google/Apple), and trying a different network. If you’re stuck in a loop, reset the session and verify you’re using the same login method as the account.
Midjourney does not support direct email/password login — you must sign in through Discord or Google. If you originally created your account with a specific email via Google sign-in, use that Google account to log in. If you cannot remember which method you used, try both Discord and Google; whichever one matches your original registration will work.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Midjourney Google login fails most often because of a browser cookie conflict, a Google account session mismatch, or an extension blocking the OAuth redirect — clear cookies for midjourney.com and google.com, open an incognito window, and try again. Make sure you select the same Google account you used when you originally registered for Midjourney, as each Google account creates a separate Midjourney profile.
Fix Midjourney login problems by clearing site cookies, disabling extensions/VPN, completing OAuth re-authorization (Google/Apple), and trying a different network. If you're stuck in a loop, reset the session and verify you're using the same login method as the account.
The 'You are not allowed to use this command' error in Midjourney Discord appears when the channel does not have the bot's slash commands enabled, when the bot lacks Use Application Commands permission in that channel, or when your account has a restriction. The fastest fix is to verify the channel permissions: in Discord, right-click the channel → Edit Channel → Permissions → find Midjourney Bot → ensure Use Application Commands is enabled.
Check if you have remaining GPU minutes, verify your prompt doesn't violate content policies, and make sure you're using the correct /imagine command.
Fix Midjourney billing issues by confirming the purchase channel, verifying the card/bank auth, refreshing your subscription status (sign out/in), and checking for pending vs posted charges. If access is still locked, contact support with the receipt/transaction ID.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Midjourney payment errors are almost always caused by one of 4 issues: an expired or replaced card, a bank block on international recurring charges, a failed 3-D Secure authentication, or billing address mismatch — go to midjourney.com/account, update your payment method, call your bank to authorize Stripe charges, then retry.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Midjourney payment failed errors are caused by bank declines, expired cards, or failed 3-D Secure authentication — update your payment method at midjourney.com/account, call your bank to authorize recurring charges from Stripe, and ensure your billing address matches your bank records exactly before retrying.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the targeted steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'rate limit exceeded' error means you have sent too many simultaneous requests — Standard plans allow 3 concurrent Fast jobs, Pro and Mega allow up to 12. Stop all requests, wait 60 to 120 seconds, switch to Relax mode using the /relax command, and resume with one job at a time.
Midjourney rate limits cap you at 3 concurrent Fast mode jobs on Basic and Standard plans — when you hit the limit, stop new requests, wait 60 seconds, then use the /relax command to switch to unlimited Relax mode if you are on Standard or higher, or simply wait for your current jobs to finish before submitting new ones.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Midjourney's refund policy allows refunds only if you have used less than 1% of your monthly image generation allocation and request the refund within a short window after billing — contact support at docs.midjourney.com with your transaction ID to request a refund. Midjourney plans start at $10/month and refunds are not available for partial months once significant usage has occurred.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Submit a Midjourney refund request at docs.midjourney.com (select Billing category) or via the #billing-support channel in the official Midjourney Discord — include your transaction ID from your Stripe receipt, registered email, and refund reason. Midjourney refunds are approved if you used less than 1% of your monthly allocation; responses arrive within 1 to 5 business days.
Midjourney refunds are available if you used less than 1% of your plan's monthly image allocation — request through docs.midjourney.com with your Stripe transaction ID and expect a response within 1 to 5 business days. Plans range from $10/month (Basic) to $120/month (Mega); partial month refunds after significant usage are not covered by standard policy.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the targeted steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Midjourney subscription renewals fail in over 80% of cases due to expired cards, bank blocks on recurring international charges, or insufficient funds — go to midjourney.com/account, update your payment method under Billing, then contact your bank to whitelist recurring charges from Midjourney's payment processor.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'too many requests' error triggers when you exceed 3 concurrent Fast jobs on Basic and Standard plans — stop submitting new requests, wait 60 to 120 seconds, switch to Relax mode with /relax if on Standard or higher, and limit yourself to 1 to 2 jobs at a time going forward.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the targeted steps below.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'usage limit reached' message means your fast GPU minute allocation for the current billing cycle is exhausted. Standard and Pro subscribers can switch to Relaxed mode to keep generating at no extra cost. Basic plan users must wait for their billing cycle to reset or upgrade their plan.
Midjourney's usage limit means your monthly Fast GPU hours are exhausted — Basic plan gets approximately 200 images, Standard gets 15 Fast GPU hours, Pro gets 30 hours, and Mega gets 60 hours. To continue generating: switch to Relax mode with /relax (Standard+), purchase additional Fast hours at midjourney.com/account, or upgrade your plan.