Before You Buy Opus: What to Test with Your Five Free Conversions
Before buying Opus, do not spend your five free conversions proving that EncoX can handle a few tiny sample clips. Use them on files that represent your real library: the kind you open most often, a subtitle-heavy video, an HDR or Dolby Vision title, your largest file, and something with multiple audio tracks. Those tests can tell you whether EncoX fits your actual routine. If the files that matter most to you produce results you cannot accept, there is no reason to buy Opus.
Five tests still cannot predict every file you have not tried. EncoX may only need to adjust the container for one video while another requires a full conversion, depending on the video encoding inside the file. Subtitles, HDR, file size, and audio tracks can also change what you should evaluate. The point is not to make all five tests look successful; it is to surface the limits that would matter to you before you pay.
1. Decide what you need to learn before you spend the five tests
The most useful test files are not demo clips downloaded for the occasion. They are files you actually keep, organize, and expect to watch on an iPhone, iPad, or Mac. Look through your own library first. Pick examples from the sources you use most, with the lengths, subtitle setups, and audio configurations that are normal for you.
EncoX has been device-tested with MKV, MP4, AVI, TS, WebM, MOV, M2TS/MTS, VOB, MPG, DV, ASF, WMV, 3GP and RMVB inputs, and it outputs MP4. The boundary for each box is in which containers and codecs have real-device readings. But the filename extension does not tell you how the conversion will behave. Two MKV files can take different paths because the video encoding inside them differs. One may only need its container adjusted, while another may need a full conversion. So the useful question is not simply, “Can EncoX convert MKV?” It is, “What happens to the MKV files I actually own?”
The five free conversions are most valuable when five real files answer one practical question: does EncoX fit the files you personally need to use?
The free allowance counts successful conversions only. Failed attempts, cancellations, and retries do not consume one, while deleting a finished output does not restore a conversion. For the exact counting rules, see the free allowance guide.
2. Why tiny sample clips can give you the wrong confidence
A tiny file removes many of the conditions that make a real decision difficult. A short clip makes waiting time look trivial. A small file creates little storage pressure. A clip with no subtitles, no HDR, and one audio track tells you almost nothing about how those parts of your library will behave.
Speed is especially easy to misread. If the video is already suitable for the target MP4, EncoX can adjust the container without recompressing the picture, and that path can be very quick. Other files require a full conversion and take substantially longer. A thirty-second sample may finish before that difference matters to you, even though a full-length movie would make the tradeoff obvious.
Instead of trying to make the first test “easy,” give every conversion a job. One should test your normal file type. Another should test subtitles. Another should test the image characteristics you care about. When each sample represents a real use case, even an unacceptable result is useful because it tells you something that can change your decision.
3. Use the five conversions on five different risks
- Test 1: the kind of file you encounter most often. Choose a real example from your normal library, not a specially selected easy case. Check whether it converts successfully to MP4 and whether the result opens and plays the way you need in your usual workflow.
- Test 2: a video whose subtitles matter to you. Text subtitles can be carried into the MP4, but ASS positioning, colors, and other styling are reduced to plain text. Blu-ray image subtitles (PGS) are read and rewritten as text, so you get a subtitle track you can restyle — and because recognition can make mistakes, this is exactly the check worth doing during the free tests. EncoX also does not import external subtitle files.
- Test 3: an HDR or Dolby Vision file. When only the container needs adjustment, the picture and its metadata are left as they are. When the file requires a full conversion, check what the rebuilt picture looks like to you and whether the colour behaviour is acceptable - that route is delivered at source depth up to 10-bit with 4:2:0 chroma. Judge the actual picture, not merely whether playback starts.
- Test 4: the largest file you realistically expect to convert. This is where you learn whether the waiting time and storage requirement fit your routine. A full conversion peaks under twice the original file size in disk usage, so check that much room on the destination before starting.
- Test 5: a file with multiple audio tracks. Check the finished file and confirm the tracks you expect are present. EncoX processes multiple tracks individually. Compatible audio is kept; incompatible audio is converted to AAC while preserving channel count and sample rate.
If HDR never appears in your library, do not waste a test on it just because it is on this list. Replace that slot with your own recurring risk: perhaps a second source of MKV files or another long video that better represents what you actually watch. The structure matters more than the exact labels: each conversion should test something you are likely to care about again.
4. Some limitations are identical in the free version and Opus
This is the distinction to keep clear before paying. The free version and Opus produce the same file quality, and there is no paid quality mode or paid speed mode. Opus is a one-time purchase that removes the conversion-count limit; it does not give the same source file a different processing result. The price lives in the pricing section of the home page. The Opus pricing guide covers the purchase details and what it unlocks.
If a limitation affects the files you care about most, discover it during the free tests. Opus removes the conversion-count limit; it does not remove the file-handling boundaries listed below.
- PGS image subtitles are recognised as text and kept as a subtitle track; recognition can make mistakes, and real-device runs cover the PGS family only, so DVD and set-top-box forms with no sample are not written as verified.
- Spatial video is flattened to regular 2D video. The app may not recognise every spatial-video file; if it recognises one, it requests confirmation before converting it and asks only once for that file.
- A 12-bit source lands at 10-bit, and 4:2:2 or 4:4:4 chroma becomes 4:2:0 while the bit depth is kept.
- DRM- or FairPlay-protected content is not processed.
- External subtitle files cannot be imported, and EncoX does not export a separate subtitle file.
- Simplified-versus-traditional information in Chinese subtitles is not preserved after conversion.
If one of those points describes a core part of your library, deliberately include that kind of file in the free tests. It is more useful to learn about a blocking limitation now than to spend all five conversions on easy examples.
5. The large-file test is really about time and free storage
Do not treat the large-file test as a stunt to see how big a file EncoX can handle. Its purpose is to reveal the practical cost of the kind of conversion you may repeat. When a full conversion is required, peak disk usage stays under twice the source size, so confirming the room available before starting is a sensible part of the test.
Use realistic duration as well as realistic size. Some files that require a full conversion take noticeably longer: the wait runs with the length of the clip, usually beyond it. That is why a ten-second sample cannot tell you what waiting for a full-length file will feel like.
For a buying decision, I would give this test more weight than a second ordinary sample. It reveals three things at once: how long you may wait, how much free storage you need, and whether that process fits the way you actually use your device.
6. After five tests, judge the recurring use case rather than the success count
Once the tests are done, separate the results into two groups. The first is “I will encounter this repeatedly, and the output works for me.” Your common files convert, subtitle behavior is acceptable, and the time and storage cost of large files fit your routine. The second is “This is a core use case, but the result is not acceptable.” Perhaps image subtitles are essential to you, or the HDR behavior on files requiring a full conversion is a deal-breaker for your archive.
If the file types you use most produce results that fit your needs, unlimited conversions may be useful to you. If your most important recurring file type produces an unacceptable result, Opus does not fix that problem, so you do not need to buy it.
Do not give a rare edge case the same weight as something you open every week. One unusual file failing may not matter to your normal workflow. The reverse is also true: four easy successes should not outweigh one failure in the exact subtitle or image scenario you depend on. The free allowance is most useful when it helps you identify that difference.
7. Boundary: what five tests cannot tell you
- They cannot predict files you did not test. Five representative samples can cover five scenarios, but they cannot expose every subtitle type, video characteristic, or damaged-file condition elsewhere in your library.
- Paying does not change the result you saw in the free version. Free and Opus output the same quality, so the free tests are valid evidence for your decision. But an untested limitation remains untested.
- One timing result is not a fixed speed. The required processing depends on the file. Some conversions are quick because only the container changes; others require a full conversion and take longer.
- A generic error will not diagnose a damaged file. Damaged files currently receive a general error rather than an explanation of exactly what is wrong.
- A spatial-video test cannot validate spatial-video preservation. Once EncoX reads that signature it flattens the file to a single-view, ordinary 2D picture - and it asks you before starting, once per file.
Think of the five conversions as representative sampling, not a certification of your entire library. The closer those five files are to what you really use, the more useful your final buy-or-do-not-buy decision will be.
Common questions
I used all five free conversions. Can I keep testing for free?
The free version counts the first five successful conversions. Failures, cancellations, and retries do not consume a conversion, while deleting a successful output does not restore one. Opus removes the conversion-count limit.
If I buy Opus, will it fix the subtitle limitations?
No. Free and Opus produce the same file result. Text subtitles can be retained, although ASS styling is reduced to plain text. PGS image subtitles are recognised as text and kept as a subtitle track, though recognition can make mistakes; external subtitle files cannot be imported.
Are a few thirty-second clips enough for testing?
They are enough only if short, simple clips are what you normally convert. If your real library includes long videos, subtitles, HDR, or multiple audio tracks, tiny samples will not reveal the waiting time, peak storage use, or those file-handling boundaries.
If a test conversion fails, does it use one of my five?
No. Only successful conversions count toward the free allowance. Failed attempts, cancellations, and retries do not consume one.
How much free space should I have before testing a 10 GB file?
If the file requires a full conversion, peak disk usage stays under twice the original size, so check that much room before starting. Whether a full conversion is required depends on the file itself.
Axiom One LLC — EncoX