Skip to content
Raghvendra Pratap Singh.
← Back to work

File Converter

Batch file conversion on your computer, with clear progress and a way to recover when a file fails.

Application development · interface and conversion workflow

The problem

Converting a folder of files should not mean uploading them to a website or repeating the same steps for every file. It also needs to be clear which outputs were saved when part of a batch fails.

Engineering decision

I put recovery in the main workflow: failed files can be retried, a running batch can be stopped, and unsupported combinations are explained before conversion. The application coordinates specialist engines rather than reimplementing every file format.

Demonstration and evidence

The browser converter is a separate PNG/JPEG demonstration, not the desktop application shown in the captures. Those captures show a local development build. Conversion fidelity depends on the format and engine; this is not a claim that every format is lossless or that an installer has been verified.

Browser converter

Interactive demo

Convert PNG or JPEG images locally in this separate browser demonstration, or use a sample batch. The desktop application is shown in the recorded captures below.

File ConverterOriginal app capture
File Converter with one saved file and one damaged file, plus retry guidance.
Results & recovery · Sample dataOpen full-size capture

How it works

The desktop interface lets you choose files, select a compatible output format and start a batch. Conversion engines run behind a controlled application interface. Each file keeps its own progress and result, so a damaged input does not hide successful conversions.

Collaboration & credits

Built on Electron and React, with conversion tools including ImageMagick, LibreOffice, Pandoc and ExifTool. My work is the application, integration and user workflow.

Verification details

The original app was exercised with HEIC images, a deliberately damaged file and document-to-PDF conversion. The run also checked cancellation, settings persistence and accessibility in several display modes.

Evidence date
Source revision
672c8c0d86b6ac68e9ec6b690d4605200a4517a2
Working tree
modified

These historical captures used a modified working tree; the exact patch was not retained. A separate clean run at this revision on 29 September 2026 verified a synthetic TIFF batch, damaged-file failure, retry and cancellation with saved outputs preserved. The broader suite timed out on Word-to-PDF, so no fresh PDF or full-suite pass is claimed. Historical capture dates and identities are unchanged.