Google Photos help and reporting
Use Photos support; preserve local items that have not finished backing up.
Live Domain Check
Run a live reachability check for photos.google.com. Compare the regional responses with the problem you see in Google Photos.
Find Google Photos help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Photo backup, library display and sharing links can fail separately.
The checker above requests photos.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Photos action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse streaming and media checks.
Use Photos support; preserve local items that have not finished backing up.
Open the website in your browser and compare it with the result above.
Open Google Photos help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Device/app version, item type/size, backup message, account storage state and time; keep personal photos private.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Google Photos.
These are troubleshooting comparisons, not claims that Google Photos is currently experiencing a particular incident.
Check whether an already backed-up item opens and whether one new item or all pending items fail to upload.
Compare the selected Google Account and backup/storage state before removing local photos or clearing app data.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Google Photos seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open photos.google.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Google Photos issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Google Photos support.
Run the photos.google.com check and compare its original timestamps and responses with your actual error. Photo backup, library display and sharing links can fail separately.
Use the community buttons on this page to share whether the service works for you. For help from Google Photos, use the official help/reporting resource linked above. Use Photos support; preserve local items that have not finished backing up.
Check whether an already backed-up item opens and whether one new item or all pending items fail to upload. Compare the selected Google Account and backup/storage state before removing local photos or clearing app data.
Device/app version, item type/size, backup message, account storage state and time; keep personal photos private.