Platform · pre-upload
Bluesky uploads and metadata
Bluesky treats images fairly raw: compression is limited and the metadata usually stays complete. Anything privacy-sensitive needs handling before upload.
On-device/No upload/Quality unchanged/No sign-up
Drop images here, or click to choose
JPG, PNG, WebP, AVIF, HEIC · 15 MB each · up to 30 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
Light compression; metadata usually survives intact
The same image in different slots — feed, story, cover — may be three separate files, and each one has to be handled.
What the platform reads
| Entry point | Notes |
|---|---|
| Image | Usually keeps the original metadata |
| Video | Transcoded, but container tags may remain |
| Link card | Depends on the source site |
Pre-upload checklist
- 11. Clean before uploading
- 22. Watch GPS and device details
- 33. Handle video the same way
- 44. Upload that copy, with no editor or forwarding in between
Common traps
- Treating Bluesky as a small platform and ignoring metadata
- Linking to a source site where the file was never cleaned
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Does Bluesky clean metadata?
Usually not completely, and its compression is conservative.
Will it be flagged as AI?
Platform policy shifts, but the data inside the file is intact.
Does cleaning affect quality?
Local cleaning does not re-encode, so no.