Post an image and get a link.
Drag an image in and copy the URL it gets. Paste it into a chat, a doc, a README or a forum post.
Drop your image here
One image, or a folder of them. straight from ChatGPT is fine
The short version
Posting an image takes three moves: drag, copy, paste.
A direct image link ends in the file name, like .png or .jpg.
A free account publishes it. No card, and your files don't train any model.
Images from ChatGPT, Claude or Midjourney work as they are.
How to post an image in 3 steps
- 1Drop the image
Drag your image onto the upload card, or click it to pick the file.
- 2Sign in and publish
Sign in with an email code, Google or Apple. About 20 seconds later the image is live at an HTTPS URL.
- 3Paste the link
Copy the URL and paste it into a chat, a doc, a forum post, a README, a ticket or an email.
That's the whole flow. No Git, no build step, no deploy pipeline.
What you need
One image file: .png, .jpg, .jpeg, .webp, .gif or .svg
A browser
An email address, or a Google or Apple account, to publish
What you get back
One link to a page that shows your image. Add the file name to the end and you have the direct image link.
Where your image actually lives
One upload gives you two useful URLs. They aren't the same thing, and the difference matters.
The direct image link
A URL that ends in the file name. The browser shows the image and nothing else. This is the one to embed in HTML, Markdown, CSS, a README or an AI answer.
The image page
The link you get when you publish. It shows the image with its name, size and an Open link. Good for sending to a person, not for embedding.
PNG, JPG, GIF, WebP and SVG show on the image page itself. Formats most browsers can't display, like TIFF or RAW, get an icon and an Open file button instead.
What a hotlink is
A hotlink, also called an inline link, is a page showing an image by pointing at the file on someone else's server. The visitor's browser fetches the file from that server, and that server pays for the bandwidth. (Wikipedia)
Some hosts block it. They swap your image for a warning, or simply return a broken image. (Namecheap)
Test the link before you share it
- 1
Copy the direct image link.
- 2
Open a private browser window.
- 3
Paste the URL into the address bar and press Enter.
- 4
If the image loads on its own, with no page around it, the link is public and it works.
- 5
If you see a page with the image on it, you copied the image page link. Add the file name to the end.
Upfling doesn't block hotlinking on a public site, so the direct link keeps working wherever it's embedded. On a password-protected site, images load only for people who have entered the password.
Your image, your rules
Plain terms, no footnote.
Free account, no card
You sign in to publish, and the free plan doesn't ask for a card. Anyone with the link can view the image without an account.
You keep the rights
Uploading doesn't give Upfling a license to your image. It stays yours.
No training on your files
Your images don't go into any AI model, and they aren't sold. It's in the Terms of Service.
Checked for phishing and malware
Once your image is live, an automated check looks for phishing and malware. Files aren't routinely read by hand. That only happens when investigating a report, answering a legal request or fixing a fault.
Retention, stated plainly
No expiry date and no inactivity purge. There's no countdown and no expiry setting to pick.
Delete the file and its URL stops resolving. A browser that already loaded it may show a cached copy for up to an hour.
If you leave a paid plan with more sites than Free allows, the older ones are paused.
Keep your own copy of anything that matters.
The full rule is on what permanent means.
Posting an AI-generated image
You made an image in ChatGPT, Claude or Midjourney, and now you need a URL for it. A plain link usually beats a platform post.
A platform post buries the image in a feed, where it lives or dies by the algorithm.
A direct link loads the file every time, wherever you paste it.
A platform may recompress, crop or strip metadata when you upload. Upfling serves the file exactly as you uploaded it.
A URL is one line of text. It fits in a doc, a ticket, an answer or a chat.
Provenance and metadata
Your generated file may carry provenance data. Images from ChatGPT ship with C2PA Content Credentials, a signed record of how the image was made. (OpenAI) The credential is cryptographically bound to the file, so tampering with the image or its history can be detected. (C2PA)
Two things follow.
- 1
A missing credential proves nothing. Re-exporting, converting, resizing or uploading to some platforms strips metadata. No credential doesn't mean the image wasn't made with AI. (Content Credentials)
- 2
Keep the original file. If provenance matters, upload the file exactly as you downloaded it, without editing, converting or resizing it first. Upfling doesn't re-encode, so the credential stays intact.
Metadata you may not want
Generated images usually carry less metadata than phone photos. A phone photo often records the camera model, a timestamp and GPS coordinates. (Comparitech)
Upfling serves your file exactly as uploaded, metadata included. So if location or device data matters:
- 1
Strip EXIF data before you upload. Your system's photo viewer or a metadata cleaner can do it.
- 2
Or upload a generated image, which rarely carries GPS data at all.
Then post it, copy the link and move on.
Posting a whole folder of images
One image is the warm-up. A generated project is usually a hero image, a few product shots, a logo, favicons and a README that expects all of them to load. Posting them one at a time and stitching the URLs together by hand gets old fast.
Drag the whole folder in instead. Every file gets its own direct link, and the folder gets one gallery page with a thumbnail of each image, so you can send a single URL.
Same three steps, different input. The folder layout and per-file links are covered in hosting an image portfolio.
Questions about posting an image
Post one image now
Drag the file in, copy the URL, paste it where it needs to go.