# File Converter Pro is a Windows converter that never sends your file anywhere

> File Converter Pro is a Python and PySide6 desktop converter for Windows 10 and 11 that handles documents, images, audio and video entirely offline, with watch folders, a Windows context menu entry, community translations and a fallback engine per format. The dependency set in the manifest is the honest description of what it can actually convert.

**Hyacinthe-primus/File_Converter_Pro** — Free offline all-in-one file converter for Windows. Converts documents, images, audio and video locally. No uploads, no internet, no dependencies. Built with Python & PySide6. Features dark/light theme, stats dashboard, achievements, and multi-engine fallback.

- Repository: https://github.com/Hyacinthe-primus/File_Converter_Pro
- Website: https://file-converter-pro.org/
- Stars: 595 · Forks: 84
- Language: Python
- License: GPL-3.0
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/hyacinthe-primus-file-converter-pro

## Offline is the pitch, and the structure backs it up

File Converter Pro is described as a free, fully offline Windows desktop application that converts documents, images, audio and video from one tool, without a browser and without uploading files anywhere. The highlights section repeats it in three parts, with no telemetry, no uploads and no internet required. Claims like that are cheap on their own, so the interesting question is whether the structure supports them. It largely does. There is no server component in the repository, the conversion libraries are all local libraries that operate on a file you hand them, and the only network client in the dependency list is the requests library, which in a converter of this kind is more likely to be there for a version check than for moving your documents. The application ships as an installer or a portable archive, states that no Python and no dependencies are needed on the target machine, and the sizes are given as around 225 megabytes installed and around 219 megabytes portable, which is consistent with bundling an interpreter and a large set of binary wheels.

## The dependency list is the real feature list

Because the tool is a thin layer over a pile of libraries, the manifest is the most useful document in the repository, and it is long. The document handling side is the deepest, with PyMuPDF for rendering and text extraction, pypdf for manipulation, pdf2docx for turning documents into Word files, pdfkit, pikepdf for the low level PDF layer, reportlab for writing documents, and scanlayer for the optical character recognition that produces a searchable text layer. The office formats have their own set, with python-docx, docx2pdf, python-pptx, openpyxl for spreadsheets, odfpy for the OpenDocument format and docxcompose for merging. Images are handled by Pillow, pillow-heif for HEIF, rawpy for camera raw files, vtracer for vectorising raster artwork, an AVIF plugin and psd-tools for layered Photoshop files. Ebooks have ebooklib, and the general conversion utilities include Markdown, pypandoc for document conversion through Pandoc, weasyprint for rendering HTML to PDF, and lxml. Audio and video run through ffmpeg-python and playsound3, archives through pyzipper, encryption through the cryptography library, and charts through matplotlib. The scheduling side uses watchdog for folder watching and APScheduler for timed jobs. Reading that list is how you know what the application can and cannot do, and no marketing sentence tells you as much.

## Multiple engines and a package layout that admits it

The project description mentions multi-engine fallback, which is the architectural idea worth understanding. Converting a PDF to an image can be done by rendering it, by rasterising pages, by running a converter binary, and by several other routes, and the failure modes differ. A fallback design tries the next engine when one does not produce a usable result, which is why such a tool can say it handles a format when it in fact handles it by three different means. The package configuration lists the module names the project considers its own, and they map directly onto the features in the readme: the application shell, the converters themselves, the dialogs, the templates, the tasks layer, the context menu integration, the achievements system and shared utilities. The per file linting exceptions are informative too, since three specific files are exempted from the line length rule, which are the user interface module, the terms dialog and the template module, and the comment attached to the first of them says it is because long lines inside HTML string literals cannot be wrapped or marked. That is the kind of detail you only find in a project whose interface is partly built from HTML.

## Watch folders, scheduled tasks and a right-click menu entry

Three features turn the application from a manual tool into something that runs on its own. The automation feature covers watch folders and scheduled tasks, and the README says the application runs as a background daemon, so a folder can be watched for new files and processed without anyone opening the program. The Windows context menu integration puts an entry on every supported file, so right-clicking a document offers to convert it with the application, which is the feature that makes the tool feel native rather than bolted on. The Windows optional dependencies in the manifest explain the mechanism, with pywin32 for the shell integration, comtypes for talking to Windows components, and winotify for desktop notifications, all three marked as Windows only. The scheduled side has a time zone data dependency, which is a small sign that the scheduler is set to behave correctly across daylight saving changes, and the achievement and statistics features are backed by SQLite, so the gamification state is local and does not need a server either.

## Translations are a drop-in JSON file

The localisation story is unusually open for a desktop application. The community internationalisation feature works by dropping a file with a .lang extension, in JSON, into the project, and no code change is needed to add a language. That is a deliberate trade of fine grained control for a low barrier to contribution, and it fits the rest of the project, which is built around the idea that a person who wants to add a language should not have to learn the codebase. The supporting detail is that the readme, the wiki and the in-app support dialog are all listed as places where a translation is welcome, and the contributing guide is the single document that covers translations, bug reports, code fixes and feature proposals. The application is also multilingual in the interface, and the project lists donation options through Ko-fi and PayPal, with the donation dialog reachable from inside the app, and states that the application will remain completely free.

## Packaging, the wiki, and a version that runs ahead of the tag

Distribution is arranged for people who do not want to build anything, with an installer executable and a portable archive on the releases page, the project website, and an itch.io page as a third route. The target is Windows 10 and 11 on 64-bit. The wiki holds the documentation that does not fit in a readme, including system requirements, notes about antivirus false positives, and PowerShell one-liners for the silent install, which is the sort of thing a sysadmin needs and which is much better placed in documentation than in a readme table. For developers the readme gives a short sequence, cloning the repository, installing the runtime and development requirements, and running the entry point from the source directory.

```bash
git clone https://github.com/Hyacinthe-primus/File_Converter_Pro.git
cd File_Converter_Pro
pip install -r requirements.txt
pip install -r requirements-dev.txt             # Dev/Build dependencies
python src/main.py
```

The licensing is GPL-3.0, the copyright line names Prime Enterprises, and the project carries a code of conduct, a security policy and a roadmap file. One small inconsistency is worth noting for anyone tracking versions, since the manifest version reads 1.0.8 while the newest published release is v1.0.7 from 2026-08-19, so the development branch is one version ahead of the artefact you can download, and the last push on 2026-10-22 is later again.

## Conclusion

File Converter Pro suits someone who converts files on a machine where the files must not leave, since the offline claim is structural rather than a policy statement, and it suits a Windows user who wants one tool rather than a web service with an upload step. It is the wrong tool for a macOS or Linux user, since the application and several of its dependencies are Windows specific, and the wrong tool if you want a converter that runs as a service or on a headless machine. Verify three things before you rely on it: which formats you actually need, since the capability of the app is the union of the libraries in its manifest rather than anything more, whether the offline claim holds on the path you care about, since a converter that shells out to a web service for one format would break that promise, and how the fallback engine behaves when a format is unsupported, since a multi-engine design is only as good as its worst engine. The licence is GPL-3.0, the newest release is v1.0.7 from 2026-08-19, and the last push was on 2026-10-22.

## FAQ

### Does File Converter Pro upload my files anywhere?

No. It is described as fully offline with no telemetry, no uploads and no internet required, and the conversion work is done by local libraries on your machine. The application ships as an installer or a portable archive that needs no Python on the target machine.

### Which file formats can File Converter Pro handle?

Documents through PyMuPDF, pypdf, pdf2docx, pikepdf, reportlab, scanlayer, python-docx, python-pptx, openpyxl and odfpy, images through Pillow, pillow-heif, rawpy, vtracer and psd-tools, ebooks through ebooklib, audio and video through ffmpeg-python and playsound3, plus archives, encryption and charts. The dependency list is the accurate description of the coverage.

### How do I run File Converter Pro from source?

Clone the repository, install the runtime dependencies with pip install -r requirements.txt, install the development dependencies from requirements-dev.txt, and run python src/main.py from the source directory. The packaged applications need Windows 10 or 11 on 64-bit.

### Can File Converter Pro run unattended?

Yes. The automation features include watch folders and scheduled tasks, with the application running as a background daemon, and it also adds a Windows context menu entry so a supported file can be converted by right-clicking it.

## Sources

- [Hyacinthe-primus/File_Converter_Pro on GitHub](https://github.com/Hyacinthe-primus/File_Converter_Pro)
- [License: GPL-3.0](https://github.com/Hyacinthe-primus/File_Converter_Pro/blob/main/LICENSE)
- [Project website](https://file-converter-pro.org/)
- [README](https://github.com/Hyacinthe-primus/File_Converter_Pro/blob/main/README.md)
- [Releases](https://github.com/Hyacinthe-primus/File_Converter_Pro/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/hyacinthe-primus-file-converter-pro