Offline decoder

One self-contained HTML file that opens TSPK v1 packages with no network at all. Keep it next to archived packages so you never depend on this website.

TinyShare offline decoder 1.0.0

Opens
TSPK v1 packages, key or passphrase
File
tinyshare-decoder-v1.html
Size
19.2 KiB, one HTML file, no other assets
SHA-256
df8f80acfa3fa16d1607f6262df1f6eb783eb92a162ca72ea32365131afaea82
Check a saved decoder fileDrop your copy to compare its SHA-256 with the published value.

Use it offline

  1. Download the decoder and store it with your packages: on a USB stick, in your archive folder, next to backups.
  2. Check the checksum. macOS or Linux: shasum -a 256 tinyshare-decoder-v1.html. Windows: certutil -hashfile tinyshare-decoder-v1.html SHA256. It must equal the value above. Save that value somewhere separate too, so you can recheck later without this site.
  3. Open it in a current Chrome, Edge, Firefox or Safari by double-clicking it. No installation, no internet needed.
  4. Choose the package and enter the key. It runs the same checks as this website and hands files over as downloads.

Built so it cannot phone home

The decoder carries its own Content-Security-Policy: default-src 'none', connect-src 'none', and a script hash that allows only its single inline script (sha256-zNvLlZI3SvnhUG9b2V+TMo/M68LGutVHsp9/fc55HDg=). Even if the code tried to send something, the browser would block it.

Same engine as the website

It is compiled from the same TypeScript engine that runs on tinyshare.com, so it applies the same limits, the same generic failure message and the same file-name checks. It is versioned: a future container version will come with a new decoder file and a new checksum.

Questions

Why would I need an offline decoder?

Encrypted archives often outlive the tools that made them. The decoder is a single file you can store with your packages and open in any current browser, even with no internet connection and even if tinyshare.com changes or disappears.

How do I know the decoder file has not been tampered with?

Compare its SHA-256 with the value published on this page (and with a copy you saved earlier). On macOS or Linux run shasum -a 256 on the file; on Windows run certutil -hashfile with SHA256. If the values differ, do not use it.

Does the decoder phone home?

No. Its own Content-Security-Policy forbids every network request and allows only its one inline script, identified by hash. You can confirm this by opening it with your network disconnected.