Two kinds of processing
QRix draws a clear line between two kinds of work. On-device processing, which covers all the video tools and most everyday tasks, runs in your browser with no upload. Cloud processing, which covers the neural AI features, sends your input to an AI model running on a server.
The distinction is not arbitrary. Trimming a video, converting a format, or removing a background with classic techniques can be done with code running in your tab. Generating a brand-new image from a text prompt, or reconstructing a 3D model from a single photo, requires large machine-learning models that cannot fit or run in a browser.
Knowing which side a tool sits on tells you what to expect: on-device tools are instant, free, and private; cloud tools take a little longer, use credits, and involve sending your input to a provider. QRix labels the cloud tools so the choice is always informed.
Video tools run on your device
All 30 video tools run locally. They convert between formats, compress footage, trim and cut clips, crop the frame, extract audio, turn a video into a GIF, and turn a GIF or an audio file into a video — without uploading your footage.
The engine behind this is the browser itself. Frames are processed on a canvas and captured with the browser's MediaRecorder into a real video file, producing MP4 with H.264 on browsers that support it and falling back to WebM elsewhere. GIF creation uses a dedicated in-browser encoder.
Because video files are large, keeping the work local is a practical win as well as a privacy one: there is no slow upload of a hundred-megabyte clip and no server-side storage of it. The limit on what you can process is your device's memory, not an upload cap.
AI tools and the cloud
The 28 AI tools include image generation, background removal, upscaling, restoration and enhancement, transcription, translation, and more. Several of the simpler ones — such as OCR — run on-device, but the generative and neural-heavy features route to cloud AI providers.
QRix runs these through an internal AI manager that connects to a chain of providers and prefers free-tier services first, falling back automatically if one is unavailable. From your side this is invisible: you submit your input, the task is routed, and the result comes back.
When an AI provider or model is not yet configured, the tool still presents a complete, working interface with an on-device preview where possible, so the feature is never a dead end. The moment cloud access is enabled, the same tool switches to full neural processing with no change to how you use it.
How credits work
Cloud AI tasks draw on a credit balance, because the underlying providers charge for compute. Every plan includes a monthly allowance: the free plan comes with 60 credits per month, Pro with 1,000, Business with 5,000, and Enterprise with a custom amount.
Different tasks cost different amounts of credits depending on how heavy they are. The image-to-3D tool, for instance, gives you a few free generations and then costs credits per model. On-device tools — all the video tools, QR, PDF, and image work — never consume credits, because they do not use the cloud.
This keeps the platform genuinely free for the vast majority of everyday tasks, while a credit system covers the real cost of the small number of features that depend on external AI compute. You always know before running a cloud task that it is a cloud task.
What we send and what we do not
For an on-device video or AI tool, nothing about your file leaves the browser — the same local model as the rest of QRix. For a cloud AI tool, only the specific input you submit for that run — a prompt, an image, or a photo — is sent to the AI provider to produce the result.
QRix does not send your file anywhere in the background, does not batch-upload your library, and does not use your inputs for anything beyond returning the result you asked for. The cloud call happens only when you press run on a cloud-labeled tool.
If privacy for a particular file is paramount, prefer the on-device tool for the job when one exists — for example, use the local video and image tools freely, and reserve the cloud AI features for the creative tasks that genuinely need them.