convrtr
Start converting

17 September 2026

4 SPECIFICATIONS

Contact

01DIRECT INQUIRIES

Reach the maintainer directly. Open channels for project questions and discussions.

For general questions, collaborations, or private security notices, contact the project maintainer directly at contact@mreshank.com or connect via GitHub at github.com/mreshank.

02ISSUE TRACKER

Public bug reports and technical issues. Tracked transparently on GitHub.

All bug reports, conversion errors, and feature proposals are tracked transparently in the public repository issue tracker at https://github.com/mreshank/convrtr/issues. ↗ Please include the input format, browser version, and error details when opening an issue.

03FORMAT PROPOSALS

Suggest new formats and codecs. Expanding client-side offline coverage.

convrtr supports 200 dedicated tools across 147 local engines. If you have a legacy file format, retro gaming asset, proprietary document, or modern codec that should run client-side without cloud dependencies, open a format request on GitHub or use our feedback portal.

04SECURITY DISCLOSURES

Vulnerability reporting and security audits. 100% on-device architecture.

Because convrtr executes 100% locally via WebAssembly, WebCodecs, and Web Workers with output: "export", files are never uploaded to any remote server. If you discover an issue in our isolated execution sandbox, please submit a responsible disclosure report via email.

DIRECT MAINTAINER INBOXcontact@mreshank.com

PGP-compatible address for private disclosures, project integrations, and developer correspondence.

LAUNCH CLIENT ↗
PUBLIC ENGINEERING CHANNELSgithub.com/mreshank/convrtr

Transparent issue tracker, format proposals, bug telemetry, and community releases.

PROJECT COMMUNICATION PORTAL

TRANSMIT AN INQUIRY

INQUIRY TOPIC
MAIL DIRECTLY VIA CLIENT ↗