Help & support

Report an issue

No account or credits are required. Reports go to the private owner inbox.

Contact SoftwareFool

Email [email protected]. Include your job ID, the time of the problem, and the message you saw. Never send your password, API key, or confidential documents.

A response time is not guaranteed. Software Fool LLC is the planned business name; it has not yet been registered.

Choosing files for Merge PDF

Merge PDF combines at least 2 PDFs in the order you choose. Each file must be no larger than 20 MiB, with 100 MiB total. The independent technical file limit is 1024 per batch. No fixed page-count limit applies. Complexity, output and worker limits still apply; these are not account-tier quotas.

Merge PDF does not support password-protected, malformed or interactive PDFs containing forms, links or comments. Other tools have different restrictions: use Unlock PDF with a password or Flatten PDF for supported interactive appearances. Keep your originals and check the merged result before relying on it.

Add files in several selections if needed, then use Move up, Move down, or Remove to arrange them. Upload controls lock during submission so the confirmed file order stays intact.

Preparing interactive PDFs

Flatten PDF converts supported visible form values and annotation appearances into static page content and removes interactive links. Keep the original if you need to edit fields later. Popup comment text and discussion threads are not exported.

Compare PDF also offers an optional Flatten before processing setting, off by default and included in its displayed comparison cost. Use this to prepare temporary copies before comparing supported interactive documents.

Password-protected and digitally signed files are not supported by flattening. A field or annotation without a reliable saved appearance fails with guidance for preparing a static copy in a PDF viewer.

Following a job

Uploading

Your browser is sending the selected files. Keep the tab open.

Queued

The job has been accepted and is waiting to process.

Processing

The files are being processed. A percentage or finish time is not estimated.

Ready

Your job succeeded. Open the job to download its available result.

Failed or cancelled

The job's credit reservation is released. A running cancellation may take time to finish.

If a submission loses its connection, keep that tab open and use its retry control. Check My jobs before starting again; a lost response does not mean that submission failed.

If status updates pause, use Check status again or Refresh status. A paused browser does not cancel the server job. Sign in again if asked, then return to the job.

Download, expiry, and Delete Now

Results stay available until their shown expiry (normally 24 hours) or you choose Delete Now. Retry interrupted downloads without converting again. Save a copy on your device. Delete Now cannot withdraw copies already downloaded.

Delete Now immediately prevents new downloads of that result and cannot be undone. It cannot withdraw copies already downloaded or a download already in progress. Stored bytes are then removed; cleanup failures are retried. Deleting a result does not cancel a completed job, refund a successful task, or remove its credit history.

Input files remain while a job is queued or processing. Successful-job uploads are deleted on the first result download or result expiry; cancelled uploads are deleted immediately. On a production failure page, you are opted out of development assistance by default. Check the box to let development keep and use your existing uploads to investigate the issue. Leaving without saved consent deletes them, with a 24-hour cleanup fallback if your browser cannot report departure. See the privacy notice for details.

Understanding credits

Available credits can be used now. Reserved credits are held for accepted jobs. A successful job uses its reservation once; a failed or cancelled job releases it. Spent records credits already used.

Each network can receive 200 guest credits once, without renewal. Registered verified customers receive 100 beta credits and can request another 100 only after using their balance and finishing active jobs. All remaining beta and legacy free credits expire when beta ends. Purchased credits are kept separately and remain in the wallet.

Review the displayed task cost before submitting. If the cost changes, review the refreshed cost and confirm again. If funds are insufficient, credits reserved by a failed or cancelled job become available again; refresh the balance after that job ends. A successful job spends its reservation. Contact support if you need help with a balance.

Credit purchases are unavailable. Monetary pricing will be announced later. Read about beta credits.

Account and API access

Verify your email before using protected account pages. Use password recovery if you cannot sign in.

From your account, manage sessions, download your account data, or review account closure. Closure has balance and active-job restrictions and retains accounting history.

Before closing your account, export any account data and download or delete the results you need to manage. Closing removes access; remaining results follow their usual expiry and cleanup.

The Python Quickstart explains API-key permissions and the quote → confirm → download flow. Copy a new API key when it is shown; revoke and replace a lost or exposed key.