Convertly is a self-hosted web application for converting, combining, and packaging common document formats. Most tools run entirely in the browser; Office-to-PDF and OCR use an isolated server-side conversion service.
- Office documents to PDF with LibreOffice
- PDF merge, split, page extraction, and rotation
- JPG, PNG, and WebP conversion
- Multiple images to PDF
- JSON, CSV, XML, and YAML conversion
- Markdown, HTML, and plain text publishing
- JSON or CSV to ICS
- ICS calendar merging
- On-device comparison of two ICS calendars by event identity and properties
- Preservation of embedded iCalendar events, recurring rules, exceptions, alarms, attendees, and timezone definitions
- JSON or CSV contacts to a multi-contact VCF 3.0 address book
- Normalized contact CSV export for contact-management imports
- OCR to searchable PDF or plain text
- Browser-side ZIP creation
Adobe PSD, PSB, AI, EPS, and native INDD conversion are intentionally outside the project scope.
Requirements: Node.js 22 or later.
npm install
npm run devRun the automated tests and production build with:
npm test
npm run buildPublic, versioned multi-platform images are published to GitHub Container Registry for AMD64 and ARM64:
ghcr.io/martythedev-tech/convertly-webghcr.io/martythedev-tech/convertly-api
cp .env.example .env
docker compose pull
docker compose up -dSet CONVERTLY_VERSION in .env to a numbered release instead of latest for repeatable deployments. For the strongest pinning, replace the image tags in docker-compose.yml with the published SHA-256 digests.
Release images include BuildKit provenance and SBOM attestations. Image tags include the semantic version, major/minor version, commit SHA, and latest.
Docker Compose builds both the frontend and conversion API. The web application defaults to port 8080; set CONVERTLY_PORT to use another host port.
CONVERTLY_PORT=8080 docker compose -f docker-compose.dev.yml up -d --buildThe API is available only to the frontend container and is not published directly to the host.
- Browser-capable conversions stay on the user’s device.
- Office conversion and OCR use temporary files that are removed after the response completes.
- The API container uses a read-only root filesystem, temporary in-memory storage, process and memory limits, and
no-new-privileges. - Files are limited to 100 MB each.
- Do not expose the application to the public internet without adding TLS, authentication, request throttling, and appropriate network controls.
For JSON exports containing complete iCalendar data, Convertly preserves the embedded VEVENT and VTIMEZONE components instead of reducing each record to a basic title and date. Generic JSON and CSV event lists are also supported.
Basic JSON example:
[
{
"title": "Project kickoff",
"start": "2026-10-20T09:00:00-05:00",
"end": "2026-10-20T10:00:00-05:00",
"location": "Conference room"
}
]CSV columns: title, start, end, description, location, and url.
The ICS comparer accepts exactly two calendar files and treats the first as the baseline. Events are matched by UID plus RECURRENCE-ID, so recurring exceptions are compared independently from their parent series. The report identifies events that are only in the first calendar, only in the second calendar, changed, or unchanged. Separate category tabs keep large result sets navigable.
When a calendar has suspicious recurrence structures, the comparer displays a warning and provides a secondary UID-only probable-match analysis. This helps identify logically related records without misrepresenting them as exact calendar matches. Timezone-definition changes and complete downloadable CSV and JSON results are also included.
Generated metadata such as DTSTAMP, CREATED, and LAST-MODIFIED, line folding, and property order are normalized so they do not create misleading differences. Calendar comparison runs entirely in the browser.
The Contact exporter accepts JSON or CSV data and creates either a multi-contact VCF 3.0 file or a normalized CSV. It recognizes common field variants for names, email addresses, phone numbers, organizations, job titles, postal addresses, birthdays, websites, notes, and contact IDs. Nested JSON contact collections are supported, and all processing stays in the browser.
Basic JSON example:
[
{
"first_name": "Ada",
"last_name": "Lovelace",
"email": "ada@example.com",
"phone": "+1 555 0100",
"company": "Analytical Engines"
}
]src/main.js— interface and conversion orchestrationsrc/calendar.js— calendar detection and iCalendar preservationsrc/ics-compare.js— structured ICS event and timezone comparisonsrc/contacts.js— contact detection, normalization, VCF generation, and contact CSV exportsrc/style.css— responsive stylingtest/calendar.test.js— calendar regression teststest/ics-compare.test.js— ICS comparison regression teststest/contacts.test.js— contact conversion regression testsserver/index.js— Office and OCR endpointsserver/Dockerfile— LibreOffice and OCR runtimedeploy/nginx.conf— frontend server and API proxydocker-compose.yml— deployment using published imagesdocker-compose.dev.yml— deployment built from source.github/workflows/publish-images.yml— tested multi-platform release publishing
Convertly is available under the MIT License.