How to share obfuscated photos through chat with Scrambl
Agree on a password, scramble on device, pick PNG or Social Safe, then reconstruct on the other phone. A simple Scrambl workflow for chat and social apps.
Key takeaways
Share the password out of band — never put it in the image QR.
Use lossless PNG when the other person can receive a file.
Use Social Safe JPEG when the app will recompress the photo.
Wrong passwords still look wrong; Social Safe reconstruct is approximate after lossy pipelines.
A four-step share that survives chat compression
If you send a private picture as a normal photo, it sits in the thread. Scrambl lets you send something that looks scrambled until both of you are ready.
Workflow
Agree on a password in a call, in person, or in a channel you already trust — not inside the image.
Open Scrambl, choose a grid, and scramble on the device.
Export PNG for file-friendly apps, or Social Safe with a Chat or Social preset when the destination recompresses JPEGs.
The recipient opens the same image in Scrambl, types the password, and reconstructs on screen.
Expect honest limits
Social Safe reconstruct is approximate after Messenger, WhatsApp, or Instagram recompression. That is the tradeoff for sending as a photo. Get Scrambl on Google Play.
Frequently asked questions
Should I put the password in the QR band?
No. Social Safe uses a high-ECC QR band for reconstruct metadata. The password is never stored there — share it separately.
When should I use PNG instead of Social Safe?
Use PNG when you can send a file without a lossy photo pipeline. Use Social Safe when the app insists on treating the share as a compressed photo.
What if the password is wrong?
The image stays unreadable. After Social Safe recompression, reconstruct with the right password is still approximate, not pixel-perfect.
