logo

Stirling-Tools/Stirling-PDF

#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere

View on GitHub ↗Jump to charts ↓Open shareable report →

Stirling-Tools/Stirling-PDF has 94k+ stars and 11k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:ApplicationCategory(s):Files, Documents & OfficeSelf-Hosting & HomelabProductivity & Business Apps
Added to GitGenius on August 30th, 2026
Created on January 27th, 2023
Open Issues & Pull Requests: 544 (+4)
GitHub issues: Enabled
Number of forks: 11,701
Total Stargazers: 94,446 (+6)
Total Subscribers: 309 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.6 hours
Mean response time: 47.9 days
90th percentile: 135.5 days
Tracked items: 1,256

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

25 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in under an hour, while "Long-term Enhancement" waits about 2 months. 52% of tracked open issues have had no activity in three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 338
New in 7 days: 25
Closed in 7 days: 75
Avg open age: 204 days
Stale 30+ days: 241
Stale 90+ days: 175

Recent activity

Opened in 7 days: 25
Closed in 7 days: 75
Comments in 7 days: 64
Events in 7 days: 160

Top labels

  • enhancement (526)
  • needs investigation (276)
  • Back End (240)
  • Front End (230)
  • v2 (83)
  • Bug (75)
  • good first issue (37)
  • question (37)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Stirling PDF is an open-source PDF editing platform that runs as a desktop app, in the browser, or on self-hosted servers with a private API.

The tool addresses the need to handle PDF operations without relying on external services. It provides over fifty tools for editing, merging, splitting, signing, redacting, converting, and performing OCR on PDFs. Users can build no-code automation pipelines directly in the UI or integrate PDF processing into existing systems through REST APIs. The platform supports deployment across multiple environments, from personal desktop use to enterprise server installations.

Stirling PDF suits organizations and individuals who require document processing capabilities while maintaining control over their data. It works well for teams needing both a user-friendly interface for manual PDF work and programmatic access for automation. The tool is particularly valuable for those handling sensitive documents that should not be sent to third-party services. The platform includes enterprise features such as single sign-on and auditing, making it suitable for larger deployments. The interface is available in over forty languages, supporting global teams.

The project maintains active community engagement through Discord and GitHub issues. Development follows a structured approach using Task as a unified command runner for builds, development, and testing. The project welcomes contributions and provides dedicated guides for adding translations and extending functionality. The codebase is written in Java and distributed through Docker, enabling straightforward deployment across different infrastructure setups.