Clean PNG Metadata
PNGs are not always “clean.” Design exports and some phone pipelines still embed text, EXIF, or XMP chunks.
Inspect metadata
Client-side parse for embedded tags/chunks the browser can see.
- Runs entirely in your browser — no upload to Rewipe servers.
- Max file size: 12.00 MB.
- Images can be wiped and downloaded here (client-side). Full mobile privacy pass stays in the Rewipe app.
Quick answer
PNG metadata can live in tEXt/iTXt chunks, eXIf, or XMP — including software names and sometimes location-related data. Inspect a PNG locally here; use Rewipe when you need a cleaned share workflow on your phone.
Key facts
| Fact | Detail |
|---|---|
| Format | PNG |
| Hidden pieces | tEXt, iTXt, eXIf, XMP |
| Inspect | Client-side |
| Wipe | Rewipe for share copies |
PNG pitfalls
- Screenshot tools and design apps may stamp software / author text chunks
- Some pipelines copy EXIF into PNG eXIf
- Transparent PNGs still carry metadata in the container
- “Export for web” presets differ — inspect when privacy matters
PNG chunk cheat sheet
| Chunk / block | May contain | Risk |
|---|---|---|
| tEXt / iTXt | Author, title, software | Med |
| eXIf | Camera EXIF incl. GPS | High |
| XMP | Rich descriptive metadata | Med |
Clean PNG metadata
- Inspect a .png. Drop it below for a client-side read.
- Review software / GPS rows. Treat high-risk like JPEG GPS.
- Wipe before publish. Use Rewipe when the PNG came from your camera roll / share sheet.
Why PNG gets its own page
- Different container than JPEG — different search intent
- Designers search for PNG metadata specifically
- Table of chunks helps AI cite accurate answers
- Avoids duplicating the JPG article
PNG metadata FAQ
| Question | Answer |
|---|---|
| Do all PNGs have EXIF? | No. Many are clean. Camera-adjacent and edited exports are the ones to check. |