Support & Troubleshooting
GUIDEDIAGNOSTICSPRIVACY-FIRST
This page helps you diagnose issues when hiding or extracting text within images using Stego. All processing is on-device; we cannot see your data, so detailed diagnostics are built into the app for transparency.
1. Quick Start Checklist
Hide Flow
- Choose a sufficiently large image (PNG preferred).
- Enter your text (UTF‑8 only).
- Review capacity indicator before embedding.
- Optionally enable raw PNG save to preserve exact bits.
- Verify extraction (auto-verification runs post-embed).
Extract Flow
- Select image suspected to contain hidden text.
- Tap extract; view result or diagnostics panel.
- Check
reasonCodeif extraction failed. - Consider recompression artifacts if image was re-shared via chat/social apps.
2. Common Extraction Reason Codes
The app surfaces structured reason codes to explain failure states:
no_magic_header– No recognizable stego header; likely no payload or it was destroyed.insufficient_header– Not enough bits even to read a header (truncated or wrong format).incomplete_length– Length field partially present; file may be cut short.length_exceeds_capacity– Declared payload length impossible for image size (tampering or corruption).truncated_payload– Header ok, but payload bytes missing before end of carrier.insufficient_capacity– Cover image did not have enough capacity at embedding time.image_too_small– Image dimension below minimum threshold for LSB embedding; fallback may trigger.crc_mismatch– Integrity check failed (data modified or wrong carrier).
Status indicators in the diagnostics panel may also include:
legacy_header– Older 8‑byte header format detected.redundant_header– Dual header redundancy successfully parsed.auto_fallback– LSB attempt declined; DCT embedding used.
3. Improving Reliability
- Prefer PNG for fidelity.Lossless formats preserve LSB embedding best.
- Avoid social media recompression.Use direct file transfer rather than in‑app forward/share.
- Stay within indicated capacity.Capacity meter shows max bytes available.
- Use raw save when precision matters.Prevents write pipelines from altering pixel bits.
- Retain original stego file.Subsequent edits (cropping, filters) can corrupt payload.
4. Tiny Image Handling
Very small images (e.g., ≤ 16×16) are at high risk for insufficient capacity and statistical anomaly detection. The app will:
- Warn you before embedding.
- Return
image_too_smallif below safety threshold. - Attempt transparent fallback (DCT) when feasible.
Tip: Upscaling a tiny image does not retroactively add meaningful cover entropy; select a naturally larger image instead.
5. Integrity & CRC Verification
Each modern payload uses:
- Magic tag: Identifies stego blocks.
- Length field: Declares byte count.
- CRC32: Detects accidental or intentional modification.
- Optional redundancy: Second header copy increases resilience to localized corruption.
If CRC fails, the app will not output partial text to avoid misinterpretation.
6. Privacy & Data Handling
Stego does not transmit your images or payload. No cloud storage, analytics, or tracking SDKs. Local temporary buffers are memory-only and cleared by normal OS lifecycle. See the Privacy Policy for formal statements.
7. Contact & Support Channels
If this guide does not solve your issue:
- Email: japalitylimited@gmail.com
- Include (optional): device model, OS version, image format, reason code observed.
- Exclude: sensitive hidden content; we cannot and do not want to view it.