Other features or issues related to Microsoft Partner Center
The error is not caused by the screenshot file format or size alone; it is a generic listing‑save failure. Screenshots themselves only have a few enforced rules, and if those are met, a 400 on save usually indicates a transient Partner Center or listing‑data issue rather than the image files.
Key points to verify for screenshots and listing data:
- Screenshot requirements
- File type must be
.png. - Orientation must be landscape or portrait.
- File size must be under 50 MB.
- For desktop screenshots, minimum size is 1366 × 768; 4K (3840 × 2160) is supported.
- For Xbox screenshots, size must be between 1920 × 1080 and 3840 × 2160.
- Do not upload screenshots for device families the app does not support.
- Maximum counts per device family (depending on package type):
- PWA/MSIX: up to 10 desktop screenshots and up to 8 for other device families.
- MSI/EXE: maximum 10 screenshots total.
- File type must be
- Listing‑page constraints that can also block saving
- At least one screenshot is required for submission; if all screenshots for all device families are removed, the listing cannot be saved.
- Product features must each be ≤ 200 characters, with at most 20 features.
- “What’s new” / release‑notes fields have a 1500‑character limit.
- If multiple languages are configured, each language’s Store listing page must satisfy its own required fields (including at least one screenshot) before the listing can be saved.
- Device‑family targeting
- If screenshots are being added for a device family that the app does not actually support, remove those and only keep screenshots for supported device families.
- For PWAs/MSIX, desktop screenshots are also shown on Surface Hub; ensure they meet the desktop requirements.
- Store logos and optional assets
- For apps that support Xbox, some Store logo images become required; missing required Xbox images can cause listing‑save failures even if screenshots are valid.
- If “only images you upload here should be used” is enabled for logos, ensure at least the required logo images are present.
- Practical remediation steps
- On the Store listing page for the affected language, verify:
- At least one valid
.pngscreenshot is present and within the allowed size and resolution ranges. - Screenshot counts do not exceed the per‑family maximums.
- No screenshots are assigned to unsupported device families.
- At least one valid
- Check all text fields on that page:
- Trim any feature text over 200 characters.
- Ensure there are no more than 20 features.
- Ensure “What’s new” (if present) is ≤ 1500 characters.
- If the app targets Xbox:
- Confirm required Xbox images and, for games with trailers, the 16:9 Super hero art (1920 × 1080 or 3840 × 2160,
.png, no text) are provided.
- Confirm required Xbox images and, for games with trailers, the 16:9 Super hero art (1920 × 1080 or 3840 × 2160,
- If multiple languages are configured:
- Open each language’s Store listing and confirm the same constraints (especially at least one screenshot per language) before saving.
- After correcting any violations, reload Partner Center and try saving again.
- On the Store listing page for the affected language, verify:
If all of the above are satisfied and the 400 persists, the issue is likely on the Partner Center side rather than with the screenshots themselves; in that case, open a support ticket through Partner Center and include the correlationId from the 400 response.
References: