Use this email address to contact PDFre and the developer directly.
Direct contact
Contact PDFre
PDFre is an independent project built by a single developer. If you have a product question, found a bug, want to report an issue, suggest an improvement, discuss licensing, or contact the developer directly, this page is the right place.
Direct contact
Send a message to the developer
Use the form for product questions, browser workflow issues, privacy questions, licensing conversations, or clear feedback about the PDF tools.
SupportBusinessFeedback
What you can write about
Product questions, broken workflows, confusing limitations, metadata issues, content corrections, privacy concerns, licensing requests, partnerships, or practical feedback about the tool pages.
You can also write if something on the site feels misleading, outdated, rough, or simply not good enough yet.
For bug reports
The most helpful messages mention which tool page you used, what file type or document shape was involved, what you expected to happen, and what happened instead.
If the issue depends on page count, encryption state, export format, or a particular option, include that context in the message.
For browser, privacy, or document-handling issues
Questions about browser-side processing, file handling, practical limits, and what the product does or does not send are absolutely welcome.
Please do not send passwords, private client records, payment details, or sensitive document contents inside the message.
For business, licensing, or legal inquiries
If your message is about licensing, embedding, partnership, attribution, copyright, trademark, or another legal topic, say that clearly in the subject line.
A short message with clear context is enough to begin the conversation properly.
Developer
PDFre was created by Sergei Solod, an independent developer who loves programming and building useful products.
To learn more about his background and resume, visit jsvar.com.
Common questions
Can I use this form for bug reports?
Yes. Clear bug reports are one of the best reasons to use this page, especially when they include the tool page and the exact step that failed.
Can I send product-copy or translation corrections?
Absolutely. Wrong wording, unclear explanations, awkward translations, or misleading promises are all worth reporting.
Should I attach private documents or passwords?
No. The safest message is a concise description of the issue without passwords, confidential documents, payment details, or private client data.
Can I send partnership or licensing questions?
Yes. Business and partnership conversations can start through this form as well.