Contact & Technical Support
Have feedback, feature requests, enterprise integration inquiries, or found a document conversion edge case? Our engineering team is here to help.
Direct Communication
Reach out directly to specialized departments for accelerated resolution:
💡 Instant Self-Help
- •Zero Server Uploads: All document conversions execute locally inside your device memory via WebAssembly. Review our Privacy Policy.
- •Troubleshooting Guides: Visit our Knowledge Hub for guides on large file processing, encryption removal, and OCR scanning.
- •Tool Directory: Browse all 48 Free PDF Tools directly on the homepage.
Send Us Your Feedback & Messages
We value your input. Whether you want to suggest a new tool, report a conversion bug, share your user experience, or ask about our privacy-first architecture, please let us know below. All messages are reviewed by our team.
Customer Support & Technical Troubleshooting FAQ
How do I report a formatting issue with PDF conversions?
Please submit the feedback form above selecting "Bug Report / Conversion Issue". Specify the source file format, browser version, and observed discrepancy. Because your files are processed locally, we never have access to your documents unless you explicitly choose to describe the layout structure.
Are there file size limitations when processing large documents?
Our client-side WebAssembly runtimes run directly inside your browser heap. Operations such as merging, compressing, or rotating can comfortably handle large batches of up to 50 files or hundreds of pages depending on your device's available RAM.
Can I suggest a new PDF tool or workflow capability?
Yes! We actively build and prioritize new tools based on customer feedback. Select "Feature Request / New Tool Idea" in the feedback form to submit your recommendation directly to our engineering team.
How is user privacy protected when submitting inquiries?
Contact inquiries are encrypted in transit and used solely to respond to your specific request. We never sell or share user contact details with third parties, adhering strictly to GDPR and CCPA privacy regulations.
Enterprise Self-Hosting, Compliance Inquiries & Privacy Audits
Organizations with strict data residency requirements (such as healthcare providers governed by HIPAA, financial institutions under SOC2 Type II, or legal firms with strict non-disclosure obligations) can deploy WeLovePDFs within their private intranet or air-gapped network environments. Because the entire processing pipeline is self-contained in static JavaScript and WebAssembly binaries with zero external telemetry, audit logs, or backend servers, our architecture is natively compliant with GDPR Article 25 (Data Protection by Design and by Default) and CCPA §1798.100.
For white-label inquiries, custom WASM build pipelines, or on-premise distribution licenses, please email partnerships@welovepdfs.com. Technical support response SLAs for enterprise users include 4-hour critical issue triage and dedicated patch releases.
To test your browser's WebAssembly performance, Web Worker thread allocation, and memory buffer limits prior to processing mission-critical documents, refer to our comprehensive step-by-step diagnostic documentation in the WeLovePDFs Knowledge Hub.
Client-Side Troubleshooting & Diagnostic Protocol
If you encounter unexpected behavior during document rendering, large file compilation, or optical character recognition:
- Browser Hardware Acceleration: Ensure hardware acceleration is enabled in your browser settings (Chrome:
chrome://settings/system, Firefox:about:preferences#performance). WebAssembly rendering leverages GPU canvas acceleration for rapid page rasterization. - RAM & Heap Allocation: When processing batches exceeding 50 PDF files or documents with ultra-high-resolution scan layers (>600 DPI), ensure at least 2GB of unallocated physical RAM is available to prevent browser tab sandbox memory throttling.
- Offline Storage Caching: WeLovePDFs leverages Service Worker caches to store WASM compilation binaries. If you need to force an update to the latest engine build, press Ctrl+Shift+R (or Cmd+Shift+R on macOS) to refresh all offline runtime caches.
Support Service Level Objectives & Response Timeframes
Our engineering support team monitors incoming inquiries Monday through Friday from 08:00 to 20:00 UTC. Standard customer feedback and feature recommendations are reviewed during weekly sprint planning meetings. Critical conversion bug reports—such as browser crash anomalies, memory buffer exceptions on specific operating systems, or character encoding rendering discrepancies—are prioritized for immediate sandbox replication and hotfix deployment within 24 to 48 hours.
Responsible Vulnerability Disclosure & Security Bug Bounty
We maintain an active responsible vulnerability disclosure program. Security researchers investigating client-side WebAssembly isolation, sandbox memory boundaries, DOM sanitization routines, or cryptographic cipher implementations are invited to submit findings directly to security@welovepdfs.com. Please provide reproducible proof-of-concept steps and allow up to 72 hours for initial validation before public disclosure.
Accessibility, Screen Readers & Assistive Technology Inquiries
WeLovePDFs is committed to universal digital accessibility conforming to WCAG 2.1 AA and Section 508 standards. If you encounter any keyboard navigation limitations, screen reader focus order discrepancies, or color contrast issues while utilizing our visual workflow builder or document workspaces, please tag your message with "Accessibility Feedback" in the form above. We promptly address assistive technology barriers to ensure an equitable experience for all users worldwide.