Technical Support • Issue Reporting
Issue Reporting & Feedback for PDF-VC
Encountered a bug, unexpected behavior, or want to suggest a new enhancement? All bug reports and feature proposals are tracked publicly via the official GitHub repository.
Open an issue on GitHubHow to Submit an Effective Bug Report
To help us diagnose, reproduce, and resolve the issue quickly, please include the following details in your issue:
- PDF-VC Version & Build: found inside the app under Help → About PDF-VC Full (e.g.,
2.0.23-beta117). - Operating System: Windows edition and architecture (e.g., Windows 11 64-bit, Windows 10 Pro 64-bit).
- Steps to Reproduce: a clear numbered list of actions (1, 2, 3) to trigger the behavior.
- Expected vs. Actual Behavior: what should have happened versus what actually occurred.
- Runtime Log: if an error occurred, copy the relevant log lines from Help → Show runtime log.
⚠️ Critical Notice: Privacy & Confidential Data
The GitHub repository is public. NEVER attach PDF files containing personally identifiable information (PII), real business invoices, confidential agreements, or credentials. If the issue is file-specific, reproduce it with an anonymized or synthetic test document.
Feature Proposals & Workflow Enhancements
Have an idea to improve usability or need support for a new PDF workflow? Use the same GitHub issue tracker with a [Feature Request] title prefix, describing:
- The practical workflow or business challenge the feature addresses.
- How you envision the interaction in the UI (buttons, context menus, shortcuts).
- Any relevant PDF standards or third-party format requirements (e.g., PDF/A, AcroForms, PAdES).