Drop files once. The interface maps the next move for you.
Clex reads file types, prepares the queue, and creates a working surface that feels immediate instead of form-driven.
12+ formats auto-classified
Image compressionPDF mergeDOCX conversion
File motion layer
clex
The file workspace that moves like software.
Prepare, route, and deliver files from one browser-native surface. Compression, transfer, fallback, and sharing all stay in the same motion system.
Browser-native Prepare files without uploads
Routing engine Direct, local, or Drive in one surface
Private by design No server storage in the transfer path
Live activity Classifying uploads
Syncing motion states
hero-shot.jpg 4.8 MB → 1.4 MB
-71%launch-brief.pdf Merged and staged
Readypricing.docx Converted to PDF
DoneShare scene Direct P2P
Sender
Receiver
Method 12 ms handoff
Status End-to-end ready
Direct P2P Primary path
Encrypted browser-to-browser delivery with zero file relay.
Local Mesh Fast lane
Same-network devices stay on the shortest path for near-instant delivery.
Drive Fallback Cloud link
If a direct route is unavailable, switch to your own Drive without leaving the flow.
CompressConvertWatermarkMerge PDFShare
Workflow system
One cinematic workflow, three product states.
The interface is designed so upload, preparation, and delivery feel like a continuous move.
System choreography 12+ formats auto-classified
Upload queue 06 live files
launch-poster.png Detected
sales-pack.pdf Merged
pricing.docx Ready
Pipeline live
Compress Convert Share
Processing depth
Direct P2P Primary route
Local lane Same-network boost
Drive link Fallback standing by
Transformations stay visible while they happen.
Compression, conversion, and preparation are treated like live states, not modal dead ends. Every step keeps the next action in reach.
Live processing rail
Queued previewsProgress choreographySuggestion engine
Routing becomes part of the product story, not a hidden backend detail.
Direct, local, and fallback routes are surfaced with confidence, so users always understand how a file is moving.
Direct, LAN, or Drive
Room creationFallback readinessPrivate defaults
Interface choreography
Every panel carries motion, status, and trust.
The site sells the product by behaving like the product: precise, alive, and confident under interaction.
Hero product demo Mock app screens with live state changes
Always in motionTransfer board Queue synchronized
Processing hero-shot.jpg
Preparing room token
Direct path approved
Status changes stay visible.
Hover lifts, scanning lines, route pulses, progress sweeps, and queue highlights all reinforce the same product language.
Buttons Soft lift, glow lock, tactile press
Cards Parallax hover and luminous edges
Feed states Animated pulses instead of dead labels
One timing curve across the site.
Entrances, sticky transitions, chip swaps, and demo beams use the same motion grammar so the experience feels authored, not assembled.
180ms micro lift
320ms state transition
700ms section reveal
Presentation Poster-scale hero with live product context
Interaction Sticky storytelling and animated command surfaces
Trust Private routing explained in the interface itself
Transfer engine
One product. Three delivery modes. Zero context switching.
The routing layer is presented like a premium control system, not a hidden technical fallback.
Primary route Direct
WebRTC browser-to-browser handoff
No file relay
Best for remote transfers
Room-based connection
Same network Local
Optimized lane for nearby devices
Fastest path on shared Wi-Fi
Low-latency room join
Great for office or studio use
Fallback Drive
Your own Google Drive as backup
Shareable links
OAuth-secured handoff
Keeps the same workspace flow