Technical Constraints

Honesty about
Limits.

The browser is powerful, but it is not a native operating system. Here's what you need to know about memory caps and file sizes.

The Browser Sandbox

Browsers (Chrome, Safari, Firefox) allocate specific RAM to each tab.

4GB
Chrome
2GB
Mobile
Auto
Firefox

File Size

~2GB Recommended

While we can stream read larger files, processing video or huge PDFs often requires loading chunks into memory. Files larger than 2GB may cause the tab to crash (Out of Memory).

Processing Speed

Device Dependent

We use your CPU. A $3000 MacBook Pro will process video 10x faster than a $200 Chromebook. We cannot make your hardware faster than it is.

Multitasking

Single Thread Focus

While we use Web Workers for background processing, browsers deprioritize background tabs. For large tasks, keep the Mojodocs tab active/visible for max speed.

Mobile Devices

Restricted RAM

iOS imposes very strict memory limits on Safari tabs. Heavy video editing or large PDF merging may fail on older iPhones due to OS-level termination.

Formats

Some formats (like proprietary RAW camera files) rely on closed-source decoders we cannot compile to WASM.

Start Time

The first time you use a tool, we must download the engine (~20MB). This happens once and is cached.

State Loss

If you refresh the page, your progress is lost instantly because data stays in volatile RAM.

WebAssembly
Client-Side Engine
Zero Latency
Processing Speed
0.00 KB
Data Retention
AES-256
Security Standard