-
Notifications
You must be signed in to change notification settings - Fork 0
Split Encoding
Jonas Resch edited this page Nov 27, 2025
·
1 revision
Split Encoding distributes your secret across multiple images. All images are required to reconstruct the message.
Your secret is divided into chunks, each encrypted and hidden in a separate image:
┌─────────────────────────────────────────────────────────────┐
│ Your Secret Message │
├─────────────────────────────────────────────────────────────┤
│ │ │
│ ┌────────────┼────────────┐ │
│ ▼ ▼ ▼ │
│ ┌────────┐ ┌────────┐ ┌────────┐ │
│ │ Part 1 │ │ Part 2 │ │ Part 3 │ │
│ │ Image │ │ Image │ │ Image │ │
│ └────────┘ └────────┘ └────────┘ │
│ │
│ All 3 required to reconstruct the message │
└─────────────────────────────────────────────────────────────┘
Split a master password across images stored in different locations:
- Image 1: Your phone
- Image 2: Cloud storage
- Image 3: USB drive at home
Share access that requires multiple people:
- Each team member holds one image
- All must collaborate to decode
Information that should only be accessible if multiple conditions are met.
- Select the Split tab in Encode mode
- Select multiple cover images (2 or more)
- Enter your secret message or file
- Enter a password
- Click Encode
- Save each encoded image
- Switch to Decode mode
- Select the Split Decode tab
- Load all the split images (in any order)
- Enter the password
- Click Decode
If you lose any image, the data is gone forever. There's no recovery option.
| Images Provided | Result |
|---|---|
| All images + correct password | ✅ Message recovered |
| Missing 1 image | ❌ Cannot decode |
| Wrong password | ❌ Cannot decode |
- Keep backups of all split images in separate locations
- Number your images or use clear naming (part1.png, part2.png, etc.)
- Test decoding immediately after encoding to verify
- Document the split — record how many parts exist
- Use the same password for all parts (required)
Data is split using a deterministic algorithm:
- Each chunk gets a sequence number (1, 2, 3...)
- Chunks are independently encrypted
- Each image stores one chunk + metadata
Each split image contains:
┌─────────────────────────────────┐
│ Split Metadata │
├─────────────────────────────────┤
│ Part Number: 2 │
│ Total Parts: 3 │
│ Chunk Hash: SHA-256 │
│ Session ID: Random UUID │
└─────────────────────────────────┘
The Session ID ensures parts from different encoding sessions can't be mixed.
| Feature | Standard | Split |
|---|---|---|
| Images needed | 1 | 2+ |
| Single point of failure | Yes | No |
| Storage requirement | Lower | Higher |
| Complexity | Simple | Moderate |
| Use case | Personal secrets | Distributed trust |