In custom website development, a client pasted a WeChat article into the CMS. Days later the images all went blank—did we miss a setting?

In most cases, the CMS editor is not broken, and no plugin was missed during installation. After a custom website development project goes live, a client copies an article from WeChat and pastes it into the CMS. A few days later, images across the page turn white. A common cause is that the paste brought in external image links, and the images still sit on the other platform’s server. Once that platform enables hotlink protection, changes its link rules, or adds authentication parameters, the images no longer appear on the front end. Based on 2026 project delivery experience, uploading images to your own media library, pasting body content as plain text where possible, and defining unified heading levels in the CMS covers most scenarios. If the client wants to freely adjust font size and color in every article, that is a content governance issue, not something a different editor can fully solve.

1. Why do images copied from WeChat turn blank across the page after a few days?

Copy and paste in a browser uses rich text by default, so text is carried over together with styles and image addresses. Images in a WeChat article are not files copied along with the article; they are addresses that remain on the original server. The CMS editor saves only that address. It looks normal right after pasting because the image is still accessible at that moment. When the other platform adjusts hotlink protection, adds authentication parameters, or the image URL itself is time-limited, blank images begin to appear on the front end.

Two other situations are often misdiagnosed as a broken editor. One is that the copied link starts with http while the website is already served over https, so the browser blocks mixed content. The other is that the article contains empty paragraphs and zero-width characters; the image position looks like a blank gap, but it is actually leftover formatting. The diagnosis differs, and so does the fix.

• All images on the page are white: usually external links are blocked or have failed in bulk, which is not the same as a single broken image.
• Only some images are white: often because the article mixes images from different sources with inconsistent link policies.
• White on mobile but normal on desktop: often because the image link restricts its referrer, or the image file is too large and triggers a loading policy.
• A blank space with no error message: may be leftover empty paragraphs or invisible characters; the image may not actually be gone.

2. First determine whether images were never uploaded or external links are blocked: a three-layer diagnosis

This type of issue rarely has a single cause. Checking three layers from lowest to highest cost helps avoid replacing the editor as soon as images turn white—only to find they are still white afterward.

1. Source layer: Paste the article again as plain text (Ctrl+Shift+V), then upload the images manually. If that works, the problem is the external links, not the editor.
2. Storage layer: Check whether these images can be found in the media library. If not, they never landed on your own server; the CMS is storing only an external address.
3. Template layer: If the images are indeed on your site but still display incorrectly, check whether the front end sets default width, height, and placeholder styles for img. Without default values, layout can easily be disrupted by a single image.

A verifiable standard can be stated more concretely: in the CMS preview of the same article, all image addresses belong to your own domain; the images still display after disconnecting the network and reopening the CMS; body paragraph spacing is consistent; and only a few individual images need manual position adjustment. Reaching this state means the problem is under control, rather than relying on operators to manually re-upload images every time.

3. Comparison of common approaches in 2026: manual re-upload, CMS direct ingestion, and third-party formatting tools

Each approach has trade-offs; none is suitable for every scenario. The main things to check are content update frequency and whether anyone is dedicated to formatting.

• Manual image re-upload: low cost and the cleanest result; a long article takes about 5 to 15 minutes, and image-heavy articles take longer (experience range). Suitable for official websites with low update frequency.
• CMS auto-downloads images from pasted content: saves manual effort, but image copyright and file size need extra confirmation. Some editors handle only certain formats, and videos and animated images still need manual fixes.
• Third-party formatting tool, then paste into the CMS: provides more consistent visual styling and suits marketing content with a dedicated editor. The trade-off is an extra toolchain, and external image links and compatibility need separate checks, typically requiring an additional review round.

A common pitfall: the client formatted the article in WeChat, it looks the same when copied, but a few days later it looks completely different, because the images were never on their own server from the start. To reduce rework, first lock down the heading levels and image widths allowed in the CMS, then have operators paste according to the rules. If the content contains many tables, animated images, or special symbols, also confirm separately how well the editor supports those elements.

4. Delivery scenario: mixed sources, part-time operators, and rules that must be written into CMS instructions

Projects often have constraints like these: client content comes from WeChat, Word, and an old website at the same time; budget and timeline are tight; there is no dedicated formatting person; and there is no time to build a custom editor. The approach is to add a fixed “paste and clear formatting” entry in the CMS, upload all images through the media library, and attach a one-page formatting rule: use only h2 and h3 for headings, use default paragraphs for body text, and keep image width within the range set in the CMS. Do a roughly 30-minute operations training at delivery. The result: in the first two weeks after launch, a few articles still needed rework; from the third week onward, most passed on the first try. The trade-off is that the operations team must accept that they cannot freely change font size and color. If this rule is not explained clearly at delivery, it often comes back later in the form of repeated complaints that “the CMS is hard to use.”

5. Boundaries: where it applies and where it does not

When it fits: content updates frequently, multiple people maintain it, source material is inconsistent, and the front end requires visual consistency. These sites are worth setting style constraints and image-localization rules in the CMS to reduce repeated revisions.

When a complex solution is unnecessary: for a small site that is mainly for display, updates only once every few months, and publishes only plain-text announcements, the CMS default editor is enough; adding extra rules only increases communication cost. Boundary statement: If the client insists that every article must be freely formatted and will not accept unified rules, the core problem is not the editor—it is whether there is a formatting standard and a reviewer. Replacing the editor cannot replace the process.

Frequently Asked Questions

After pasting into the CMS, images show as blank. Does the editor not support images?

Mostly no. Copied images are often external links. They go blank after the other platform enables hotlink protection or changes the link. Re-uploading the images to your own media library usually restores them.

Pasting as plain text loses links and bold text. Is there a middle ground?

Yes. For articles with many links, first paste with formatting, then use “clear formatting” paragraph by paragraph. Or write the body as plain text first and add links separately later; with a clear order, it is harder to miss any.

If we switch to another rich text editor, will the white images be fixed?

Only partly. If image sources and front-end default styles are not addressed, images may still turn white after the switch. It is better to locate the issue with the three-layer diagnosis first, then decide whether to switch.

Can WeChat articles be synced directly to the website CMS?

Direct scraping and syncing is not recommended. Platform content depends on its own styles and resource links. The common approach is to copy the body, localize the images, reset heading levels, and then publish.

Should the CMS let clients change font size and color themselves?

It is not advisable to open that up to non-designers. The more style options there are, the harder it is to keep the front end consistent. A common approach is to provide only limited heading levels and body styles, and handle special styles as separate requests.

If you are about to deliver a custom website with frequent content updates, first write three things into the CMS instructions: image localization, heading levels, and image width. Then decide whether to switch editors. Small sites with little content and a single source do not need extra configuration for this. For sites maintained by multiple people with mixed sources, setting standards first saves more rework than switching tools first. The specific choice depends on the actual update frequency and formatting requirements.