QRStream
中文 · Web receiver · User guide
Transfer files through QR code streams: display them on a computer, then recover the file with a phone camera or from a recording. RaptorQ is the default codec; legacy LT streams are also supported by the CLI.
Quick start
Requires Python 3.10 or newer. Install with pip (or uv tool install qrstream):
pip install qrstream
Display a file as QR codes on your computer:
qrstream encode report.pdf
On your phone, open the Web receiver, allow camera access, point at the screen and press the red shutter. Save the file when recovery finishes.
The browser supports V4 / RaptorQ streams. It processes camera frames and file contents on your device, without uploading them. Downloads are named qrstream-output.bin; rename the file to its original extension.
Camera controls
- Red shutter: start or pause reception. Pause retains collected blocks.
- Stop: clear collected blocks and progress while keeping the preview running. Confirm first if data has been collected.
- Resolution: tap the upper-left label to cycle through supported modes; file progress is retained.
- Details / save: open receiver information or save the recovered file. The ring reaches 100% only after recovery.
Video files
Create a QR video, or recover a file from a recorded video:
qrstream encode report.pdf -o report.mp4
qrstream decode recording.mp4 -o recovered.pdf
Use qrs as a short alias. Run qrstream encode --help or qrstream decode --help for options.
Documentation and development
- User guide: full options, calibration, Python API, Web development and troubleshooting context.
- Architecture: modules, protocols and test tooling.
- Contributing: development, branches, CI and releases.
To work from this repository:
git clone https://github.com/ddddavid-he/qrstream-enhanced.git
cd qrstream-enhanced
uv sync --dev
Web changes merged into main are built and deployed by the Pages workflow.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for qrstream 0.10.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qrstream-0.10.5.tar.gz | 65.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qrstream-0.10.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.0 MB
Release files / qrstream-0.10.5.tar.gz
| Download URL | qrstream-0.10.5.tar.gz |
|---|---|
| Size | 65.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3dcd3e6a78ec54c66a161c0b60909ae9632ed3ebe82323d4d51e85ac975d4277
|
|
BLAKE2b-256 checksum How to use checksums |
519f7d181e371fa3fbe75109b5539ba89628fdf8d4baab41a3778e0c873486a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / qrstream-0.10.5-py3-none-any.whl
| Download URL | qrstream-0.10.5-py3-none-any.whl |
|---|---|
| Size | 132.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4426ffdb3aee9fc22e317b3b2ba6849466c22221fe09a8bf7ea056f88b1fb03
|
|
BLAKE2b-256 checksum How to use checksums |
c58e3e2c458a4db87c89f94702195a9002b6a41fcf5270cb0825ba14619c3357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log
