Others

How to Fix HTTP Error 400 in Microsoft Publisher Picture Borders

Guest Writer Oct 10, 2026 871 views

Question details

Users experience an HTTP 400 Request-Header error when attempting to add a picture to a custom AutoShape border in Microsoft Publisher.

How to Fix HTTP Error 400 in Microsoft Publisher Picture Borders

Product: Microsoft Publisher
Device & OS: not provided
Scenario: Selecting an online or local picture to apply as a custom border for an AutoShape.
Observed behavior: The application displays an HTTP 400 error instead of applying the image, preventing the user from successfully inserting the custom picture border.

Before you start

Ensure your internet connection is stable, as HTTP 400 errors in Microsoft Publisher are frequently tied to temporary server connectivity problems when fetching online resources or communicating with Microsoft services.

Solution 1Recommended

Restart Microsoft Publisher and Retry

Since this specific HTTP 400 error is typically caused by a temporary server-side glitch, waiting a short while and restarting the application usually resolves it.

Many users report that the HTTP 400 error when adding custom borders in Publisher is temporary. It often resolves itself without requiring any deep technical troubleshooting or software reinstallation.

Close your document

Save any progress on your current Publisher document and completely exit the Microsoft Publisher application.

Wait for server recovery

Give the Microsoft online services some time to resolve any background connectivity or routing issues. This can take anywhere from a few minutes to a few hours.

Relaunch and attempt again

Open Microsoft Publisher again, navigate to your AutoShape, open the border formatting settings, and try inserting your custom picture once more.

Temporary Server Downtime: If the error persists after several hours, the Publisher service might be experiencing broader downtime. You can check the Microsoft 365 Service Status page for live updates.

Solution 2

Report to Microsoft Support

If the problem persists for an extended period, you may need to escalate the issue to Microsoft Support for a permanent fix.

Free Microsoft Office alternative

Design Stunning Page Layouts Offline with WPS Office

Tired of your workflow being interrupted by server errors in Microsoft Publisher? Switch to WPS Office, a powerful and lightweight productivity suite. Create beautiful documents and page layouts without relying on unstable server connections, while enjoying seamless compatibility with standard document formats.

1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
2. Install WPS Office: Run the setup file and follow the quick on-screen instructions to install the suite.
3. Start creating layouts: Open WPS Writer to access powerful text wrapping, shape formatting, and image insertion tools for your next layout project.

Completely free and lightweight alternative to Microsoft OfficeExcellent format compatibility with Microsoft Word, Excel, and PowerPoint filesInsert custom images, shapes, and borders smoothly without server-side HTTP errorsFamiliar user interface that requires no steep learning curve

Frequently Asked Questions

What does an HTTP 400 Request-Header error mean in Microsoft Publisher?

This error generally indicates a communication failure between Microsoft Publisher and Microsoft's online servers. It often occurs when the software sends a malformed request or tries to fetch online pictures and border resources that are temporarily unavailable.

Do I need an active internet connection to add an AutoShape picture border?

If you are inserting a locally saved image from your computer's hard drive, you shouldn't strictly need an internet connection. However, if Publisher is attempting to access the Microsoft online content library or Bing image search to find the border, an active and stable connection is required.

Can I fix this HTTP 400 error by reinstalling Publisher?

Reinstalling Microsoft Publisher is rarely necessary for this specific error. Because it is almost always a temporary server-side issue or a transient network glitch, simply waiting for Microsoft to resolve the server status and restarting your app is the most effective approach.

Office Quick Solutions