Help centerBack to app

My shared page looks broken or the images are missing

Usually the page is pointing at images or styles that live only on your computer. Here is why, and how to fix it.

Updated July 1, 20263 min read

You pasted your page in, it looked perfect on your screen, and then the link you sent shows broken images or plain, unstyled text. This is the most common snag when bringing a page in, and it has a simple cause.

Why it happens

Your page points at files using a location that only exists on the computer that made it, like images/logo.png or ./style.css. Those files sit in a folder on your machine, not on the web. So once the page is a public link, there is nothing at that location for anyone else to load.

A telltale sign: the page looks fine when you open your original file on your own computer, but loses its pictures or styling once it is shared. The page itself came across. The files it points at did not.

How to fix it

coeditapp.com/p/summer-pass
Upload asset
/api/content/logo-a91f.png/api/content/hero-7c02.jpg
Upload the missing file, then point the page at the link Coedit gives you.
Why do my images work on my computer but break when I share the link?
The page points at files stored on your computer (a location like images/logo.png). Those files are not on the web, so a shared link has nothing to load. Upload them to the project, or import the whole folder, then point at the Coedit link.
Why is my page plain and unstyled after sharing?
Your styles are probably in a separate .css file the page links to, and that file did not come across. Import the folder or .zip so the stylesheet travels with the page, or paste the styles into the page itself.
Do fonts and scripts work the same way?
Yes. Anything loaded from a local folder breaks once the page is public. Upload it as an asset, or point at a full https://... link.
Was this article helpful?
← All Bring work in from any tool articles