Paste your art on any website. Keep a door into it.
A published scene is a native-resolution PNG at /<id>.png — CORS *, no watermark, no expiry. Drop it on a commission sheet, a shop, a README. The same address without .png is the picture as a place.
Imgur compresses, watermarks, and forgets. A CDN bucket is a file with no room behind it. Here the hotlink is a render of a scene you still own: unpublish it and the image leaves; open it and someone can walk around inside.
Use it on your website
The PNG is a normal image URL. Drop it into a personal site, a shop, a blog, a commission sheet, or a portfolio — anywhere an <img src> or markdown image works. You do not need an account on the other site, and you do not need to re-upload the file there.
- HTML:
<img src="https://thinkwith.pictures/<id>.png" alt="…"> - Markdown / README / a blog:
 - CSS:
background-image: url("https://thinkwith.pictures/<id>.png")
Browsers may fetch it from any origin: the response sends Access-Control-Allow-Origin: *. Linking the image back to the scene (the same URL without .png) is optional — visitors who follow it land in the picture.
What you actually get
ThinkWith.Pictures stores images inside scenes. When a scene is public, we serve a native-resolution render of that scene — background plus the objects on it — as a regular image file:
https://thinkwith.pictures/<id>.png— lossless, native resolution, the usual hotlink for your sitehttps://thinkwith.pictures/<id>.webp— the same render, smaller, used for cards and previews- JPEG is available the same way if you need it
How to get a PNG URL
- Create a scene. Sign in, upload an image as the background, and place any objects that should appear in the picture.
- Publish it and allow guests. Renders exist only for public scenes — published, with guests allowed. Private scenes have no hotlink.
- Paste it on your site. Take the scene id from the scene’s public address and append
.png. Example:https://thinkwith.pictures/226041760427315575.png. That URL is what you put in the image tag on your own page.
This is not Dropbox. There is no generic “upload a file, get a CDN URL” bucket. The hosted image is a scene: someone who opens the URL without .png is in the picture, not looking at a download. If you only need a dumb file host, this is the wrong tool. If you want a picture that is also a place — a portfolio room, a clickable world — that is the point.
Limits, stated plainly
- Public scenes only. Unpublished scenes, or scenes that forbid guests, are not served as
.png. - Revocable. Unpublish or turn guests off and the render goes away. Cache headers are short on purpose; this is not an immutable object.
- Capacity, not a paywall. Creating and storing scenes spends strain. Hosting the public PNG is part of that scene, not a separate paid CDN plan.
Questions
- Can I use this on my own website?
- Yes. That is the point of the PNG URL. Embed it on a site you own, a shop, a blog, or a portfolio. CORS allows any origin, so your domain can load the image directly — you do not have to proxy it.
- Is this free image hosting?
- Public scene renders are free to hotlink. Creation is free. It is not a generic Dropbox-style host: the file is a picture of a scene you can still open.
- Is there a watermark or expiry?
- No watermark and no expiry on the public render. CORS is *. If you unpublish the scene or disallow guests, the render goes away.
- Does the PNG include objects on the scene?
- Yes. It is a native-resolution render of the scene as visitors see it, not the bare background file.