Build
We Want PDF is in active build. Core tool rollout starts with merge, split, compress, and convert.
Pricing

One public tool layer, then paid depth where it actually adds value

We Want PDF keeps the core web tools open for public use, then adds paid value through higher limits, faster queues, collaboration, retention, and API access instead of hiding basic PDF tasks behind signup walls.

Available now

Free

Anonymous public access to the live web-tool library with standard limits, shared queues, and self-serve trust and help content.

  • Core PDF tools without forced signup
  • Standard submit, status, and download rate limits
  • Short-lived temporary retention only
Planned next

Pro

Optional accounts are now live for repeat users. Higher limits, faster queue treatment, and synced retention still sit in the next paid layer once billing and premium controls are production-ready.

  • Optional accounts without gating the core public tools
  • Higher upload caps and faster queue priority
  • Up to 24-hour result retention
  • Priority support and workflow-oriented usage
Workspace tiers

Team, Business, Education, API

Shared billing, admin controls, domain policies, and token-based API quotas sit on top of the same public runtime once those controls are production-ready.

  • Team workspaces with shared reporting and seat controls
  • Business and education packaging around retention, support, and policy needs
  • Separate API quotas so paid traffic does not compete with SEO traffic

Access policy

The non-negotiable rule is simple: high-intent public tools stay accessible without a signup wall.

Retention and support

Free stays short-lived and self-serve. Paid web plans extend retention and support, while contract plans control those policies explicitly.

API isolation

API quotas are planned as a separate paid lane so automated usage cannot quietly degrade public organic traffic performance.

Conversion paths live today

Start with a real tool, then move into the right path

The strongest conversion path today is product-first: solve the file problem, read the trust policy that matches the use case, and then step into business, education, or future API planning only where it fits.

Trust center

Trust pages

These pages are written to stay aligned with the actual product build, so the trust center grows with the platform instead of becoming detached marketing copy.

privacy

Privacy

Review the privacy posture and product handling principles for We Want PDF.

Read page
security

Security

Learn how the We Want PDF platform is being structured to protect internal services and user file processing.

Read page
retention

File retention

Understand how We Want PDF plans to handle temporary files, deletions, and result availability.

Read page