Back to blog

Gallery / P5 · EncoX

Where EncoX Processes Your Video: Conversion Happens on Your Own Device

When you convert a video with EncoX, the conversion happens on your iPhone, iPad, or Mac. The video file itself does not need to be handed over somewhere else first. For a large or private recording, that changes the workflow in a practical way: EncoX can start from the file already on your device, with no extra wait to hand the file over and take the result back, and with one fewer step where the video file goes to an external location for processing.

That does not mean every piece of data always stays on one device. EncoX has one separate item related to its free allowance: a simple conversion-count integer can sync across your own devices through iCloud Keychain when it is enabled. That count contains no video, subtitle, or filename information. This article is about where the video is processed, not a blanket guarantee about every possible security risk.

1. The short answer: conversion does not require handing the file over somewhere else

After you choose a video from Files or Photos, EncoX reads and processes that file on the device you are using. When the conversion finishes, it creates a new MP4. It does not replace the original file, and it does not move the original out of its existing location. Whether that file later goes into a system backup depends on the backup settings of your own device - that layer is not in our hands.

EncoX performs video conversion on your device: conversion does not require handing the file over somewhere else, and the result is a new file while the original remains in place.

That is an important part of what EncoX actually does. Its job is to convert a video into an MP4 that is easier to open in common iPhone, iPad, and Mac playback situations, rather than requiring the source file to be sent away for processing and returned later. For the broader product role, see What is EncoX?

2. What changes compared with a workflow that hands the file over first

For most people, the meaningful difference is not architectural terminology. It is the number of steps you have to wait through. A workflow where the video has to leave your device first usually adds two transfers around the actual conversion: sending the source file out, then retrieving the finished file afterward. With large media, those transfers can become substantial on their own.

EncoX keeps the conversion on the current device, so those two transfer stages are not prerequisites for processing the video. The device still has to read the source, perform the conversion, and write a new file, so some jobs can still take time. The practical benefit is narrower and more accurate: you avoid the extra wait of moving a multi-gigabyte source out and bringing the result back.

On-device conversion does not mean zero waiting; what it really removes is the extra wait of sending the source file out and then bringing the finished file back.

3. Why this matters more as files get larger

If the file is a 10 GB, 20 GB, or larger family video, camera export, or meeting recording, simply transferring the source can become a major part of the experience. A slow or unstable connection can stretch that step further. Because EncoX works from the file already on the device, you do not have to finish sending the entire source somewhere else before the app can process it.

Large files are not automatically fast to convert, however. EncoX chooses its treatment based on what is actually inside the video. Some files can be handled by changing the container while without recompressing the picture, which is much faster. Others require a full conversion and will take noticeably longer. The useful expectation is therefore: large files avoid the extra hand-over and retrieval time, but actual conversion time still depends on the file itself.

4. Where the original and the converted file live

The file you choose from Files or Photos is the original. EncoX reads it for conversion, but does not rename, relocate, or overwrite it. The finished output is a separate MP4, so you can keep the source and the converted copy side by side.

That is especially useful when the source is a personal recording you do not want altered. The tradeoff is local storage: the new file takes additional space, and full conversions can require more temporary room while processing. A known boundary is that peak disk usage for a full conversion stays under twice the source size, while a container swap needs room for the finished file alone. That storage requirement is on your own device.

5. The one separate sync item: the free-conversion count

Conversion does not require handing the file over somewhere else, but EncoX does have one data point that is separate from the media-processing path. The free version counts the first 5 successful conversions. A simple integer representing that count can sync through iCloud Keychain across your own devices, so an iPhone, iPad, and Mac using the same Apple ID can share the same allowance.

The synced value is only the count. It does not contain any video, subtitle, or filename information. If iCloud Keychain is turned off, the sync does not take effect and different devices may show different counts. For the details on what counts toward the five free conversions and how the one-time Opus purchase works, see What is free in EncoX?

The item that can sync between your devices is the free-allowance count integer, not your videos, subtitles, or filenames.

6. “Conversion does not require handing the file over” is not a complete security guarantee

Being specific about processing location is useful because it tells you one concrete thing: EncoX does not need to send the video file away as a prerequisite for conversion. If the concern is a private family recording or an internal meeting capture, there is no separate “hand the whole video over so conversion can happen” stage in that workflow.

That statement should not be stretched into a broader promise. Device security, account access, backups, the place where you later save the output, and the permissions of other apps are separate questions. The accurate claim stays scoped to the file and the conversion task: conversion itself does not require handing the video file over somewhere else.

7. Boundaries: what on-device conversion does not fix

If your first question is “Does this private video have to be sent somewhere else before it can be converted?”, processing location is more useful than a vague privacy slogan. EncoX has a clear answer to that narrower question: it reads and writes the video on your device, while still being explicit about the allowance-count sync and the product’s other limits.

Frequently Asked Questions

When I convert a video with EncoX, does the file get sent somewhere else for processing?

No. Conversion does not require handing the video file over somewhere else. EncoX performs the conversion on your device and creates a new MP4, while the original file remains where it was.

Do I need an internet connection while converting?

The conversion itself does not depend on handing the video file over somewhere else first. Separately, the free-allowance count can sync across your own devices through iCloud Keychain when that feature is enabled.

Does EncoX store my video somewhere else?

The video file used for conversion does not need to be sent elsewhere for processing. EncoX reads the source on your device and writes a new output file; it does not replace or move the original.

If my video is huge, will the conversion be fast?

Not necessarily. Keeping the work on-device removes the extra wait of sending the source file out and bringing the finished result back, but conversion time still depends on the video itself. Some files only need a container change and are much faster; files that require a full conversion take longer.

Will EncoX overwrite my original video?

No. EncoX creates a new MP4 and leaves the original file in place. You do need enough local storage for the new file and, in some cases, additional temporary space during conversion.

Axiom One LLC — EncoX