Overview
UniConverter collects the jobs that usually take four separate tools and puts them behind one window. Format conversion across the video and audio containers, compression to a target file size, basic trimming and cropping, subtitle handling, disc burning, screen recording and a set of small utilities for merging, watermarking and metadata editing.
Conversion is the core and it is built for batches. Drop in a folder of files, pick one output preset, and the whole set is processed with hardware acceleration on the current GPU families. Device presets cover phones, tablets, consoles and editing formats, so a batch of camera clips becomes editable footage without hunting through codec settings.
Compression is the feature that keeps people coming back to it. Set a target size or a quality percentage and the tool works out the bitrate to reach it, with a preview of a short section so the result can be judged before committing to a long encode. For anyone who regularly hits an upload size limit, that alone replaces a lot of guesswork.
What it does well
Batch conversion
A whole folder converted against one preset with hardware acceleration, rather than one file at a time.
Target size compression
Set a file size or quality target and let the tool derive the bitrate, with a preview section before the full encode.
Editing basics
Trim, crop, rotate, merge, watermark, add subtitles and adjust audio levels without opening a full editor.
Recording and burning
Screen and webcam capture with system audio, plus disc burning with menu templates for playback on a standard player.
Utility set
Metadata editing, format inspection, GIF creation, audio extraction and a batch renamer around the conversion core.
Changes in this build
- Hardware acceleration extended to the current AMD and Intel GPU families, not only Nvidia.
- Compression preview added so the result can be judged before the full encode.
- Subtitle handling improved for embedded tracks in unusual containers.
- Batch queue reworked with per-item settings overrides.
- Faster startup with the utility modules loaded on demand.
What is in the package
- UniConverter installer, 64-bit
- Conversion engine with device and delivery presets
- Screen and webcam recorder
- Disc burning module with menu templates
- Multilingual interface files, 16 languages
System requirements
| Processor | Intel or AMD 64-bit, quad core recommended |
| Memory | 4 GB minimum, 8 GB for 4K conversion |
| Graphics | GPU with a hardware encoder for acceleration |
| Storage | 2 GB free plus space for output |
| Display | 1280 x 720 minimum |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Extract the archive and close any running instance.
- Run the installer to the default location.
- Apply the included configuration step before the first launch.
- Enable hardware acceleration in preferences if it is not detected automatically.
- Block the updater so the configuration is not replaced.
Before you start
Hardware acceleration is much faster but slightly lower quality at the same bitrate, use the software path for archival work.
The output folder defaults to the system drive, move it before running large batches.
Letting it update will replace the configuration.
Questions about this title
Can it hit a specific file size?
Yes, set the target size and the tool derives the bitrate to reach it.
Does it record the screen?
Yes, screen and webcam capture with system audio is part of the package.
Which formats are supported?
The common video and audio containers and codecs, with device presets for phones, consoles and editing formats.
Is batch processing included?
Yes, a folder can be queued against one preset with per-item overrides.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.