Help
Why Your Image Link Is Not Displaying and How to Fix It
If your image link shows a broken icon, alt text, or nothing at all, work through two questions in order: does the URL load the image by itself, and does the place you pasted it accept external images?
Updated
Step 1: Open the exact URL in a new tab
Copy the full link from your completed Yoink upload result (it starts with https://files.yoink.zip/) and paste it into a fresh browser tab.
- The image does not load at all: Make sure you copied the link from the completed upload result, not the page address mid-upload. Then see file link not working.
- The image loads fine on its own: Continue below.
Step 2: Check the embedding syntax
Different platforms expect different markup, and the raw image URL is not interchangeable with formatted tags.
- Markdown (GitHub, many docs tools): use
with the image URL itself, per the GitHub formatting guide. Use the Preview tab before committing. - HTML: the
srcmust point at the actual image file, per MDN's images guide:
<img src="https://files.yoink.zip/your-file-id/photo.png" alt="Team photo from the launch event">- phpBB forums: use
[img]URL[/img], and the image must be accessible on the web, not on your local disk, per the official BBCode guide. Note that administrators can disable BBCode or the img tag per board.
Common mistakes:
- Pasting a share page URL instead of the direct file URL.
- Truncating the link, adding a trailing parenthesis inside the tag, or including spaces.
- Mixing up display syntax
with a plain link[text](URL)in Markdown.
Step 3: Rule out format and policy problems
The host blocks or restricts external images
Many sites, forums, and chat platforms control whether externally hosted images render. Alt text appearing where the image should be means the resource failed to load or was blocked by policy; it is not proof the host is at fault, and it is not proof your file is broken. Ask the site admin or moderator rather than trying to bypass security controls.
The format is not really what the extension says
Renaming a file to .jpg does not convert it. An HEIC photo saved with a .jpg name still may not render in browsers that do not support HEIC, and saving an HTML page as .png does not make it an image. Browser media and image support depends on the actual format, per MDN's format documentation.
Content-Type mismatches (API users)
Browser display depends on the Content-Type served with the file. The Yoink browser uploader sends your selected file with its own type, but the legacy raw-body API path does not preserve HTTP Content-Type metadata. If you uploaded via the API and rendering matters, switch to the browser or presign flow and check the docs. A presigned upload URL is for uploading only; it is not the public file URL.
Quick checklist
- URL opens the image standalone in a new tab.
- Full URL copied from the completed upload result, HTTPS included.
- Correct syntax for the platform (Markdown, HTML, BBCode).
- Real image format that browsers support.
- The destination site permits external images.
A note on link longevity
Yoink links are public and there is no guaranteed file lifetime, so an image that worked before may stop loading if the file is gone. Keep your originals, and see limits and retention before relying on a link long term.