Five practical ways to use Decimen across disconnected devices

Why it matters

Decimen shows that a screen and camera can bypass unavailable or restricted networks, but the optical channel creates its own security and data-governance boundary.

Decimen is most useful when a file needs to cross a device boundary without a cable, shared network, account or pairing process. These are its five strongest practical uses, along with the operational limits that matter.

1. Move approved files off restricted workstations

Use Decimen to transfer a modest, nonconfidential document, screenshot, diagnostic bundle or configuration file from a workstation where removable storage, personal devices, consumer cloud services or external network connections are unavailable.

This does not make the transfer inherently secure. Firewalls and network monitoring never see a packet, but data still crosses the boundary through the workstation's display and the receiving device's camera. Organizations should treat cameras and displays as transfer interfaces rather than assume that blocking USB drives and wireless connections closes every exit.

Crawley's privacy documentation states that the channel is not encrypted. Any camera with a view of the sending screen can capture the stream. The SHA-256 check detects corruption but does not provide confidentiality.

That makes Decimen unsuitable for casually transmitting credentials, private customer records or other sensitive material in a shared room. An optical link is not a secure cross-domain system simply because the devices lack a network path.

2. Exchange files in disconnected field environments

Technicians can use Decimen to move a configuration file, manual, diagnostic bundle or set of photographs between devices without waiting for cellular service or creating a local hotspot. It can also carry a boarding pass, map, contact card or text block when conventional sharing services are unavailable.

Prepare the receiver before going offline. The hosted Decimen app works offline after the first visit because it caches the application and decoder. Crawley also provides standalone sender and receiver pages through Decimen's offline distribution options. Those pages contain the required code without fetching external scripts or stylesheets.

Mobile browser rules affect deployment. Decimen's documentation says iOS Safari and Android Chrome will not grant camera access to a receiver opened directly from a local file:// URL. On phones, the cached hosted app or a locally served HTTPS version is the more practical receiver.

3. Bridge devices with incompatible sharing systems

Use Decimen for one-off transfers between devices whose native sharing tools do not interoperate. A visitor can send a document to a managed phone without signing into email. A developer can retrieve a log or screenshot from a test machine. A presenter can hand off an asset across operating systems without exchanging contact details or joining the same network.

The quick-start process consists of opening the sender, selecting a file and pointing the receiver's camera at the animated code. The receiver offers the file only after its hash check passes.

Text snippets disappear when the tab closes, while saved files go to the browser's normal download location. Received audio and video can remain temporarily in the browser cache until another transfer replaces them or the user clears the cache.

4. Distribute local files from a fixed display

Decimen's demo mode can turn a fixed display into a lightweight distribution point for exhibitions, classrooms, repair counters or event booths. An unattended sender can repeatedly transmit a bundled brochure, schedule, software package or media file for nearby visitors to scan.

The demo mode restricts the sender to bundled files, but Crawley's documentation cautions that the configuration is not a hardened kiosk. Anyone with keyboard access can open developer tools. Treat it as a local distribution mechanism, not an access-control system.

5. Send small files through an unreliable visual link

Decimen supports files up to 64 MB and text snippets up to 4 MB, but its published performance makes it better suited to documents, images, configuration files and short media clips than bulk storage transfers.

Crawley's latest published benchmark recorded 418.5 KB per second of sustained goodput from a 49-inch desktop display to an iPhone 17 Pro Max. A phone-to-phone test reached 199.2 KB per second. Both used a 1 MB file, with the desktop-to-phone transfer completing in 2.5 seconds and the phone-to-phone run taking 5.1 seconds.

At those rates, a 64 MB file would take roughly 2.6 minutes in the desktop-to-phone setup or 5.5 minutes between phones, before accounting for differences in cameras, displays, lighting or compression.

The fountain-coded stream tolerates missed frames. Because the optical channel has no return path, the sender continuously produces frames and the receiver reconstructs the file after collecting enough distinct frames in any order. A blocked view or missed QR frame extends the transfer instead of invalidating the entire sequence.

For founders and operators, the practical rule is straightforward: use Decimen for small, authorized transfers when devices cannot share a network or common transfer service. Its lack of encryption and ability to bypass network visibility make policy, physical access and camera placement as important as the transfer itself.