PDF tools on iPhone and Safari

Does BestPDFInTheWorld work on iPhone?

It does, with nothing to install. Open the site in Safari and all thirty-three tools are there: merge, split and extract, rotate, delete pages, PDF to Word, PDF to image, images to PDF, sign, number pages, watermark, compress and password protect.

Processing still happens on the phone. No file is uploaded to any server, on iPhone as anywhere else,This tool is part of the Premium subscription, EUR 1.99 a month, which removes the limits on every tool and adds OCR. Sign PDF opens on the free plan, with one signature a day.

It works on iPad too, and the behaviour is the same: iPadOS shares the same browser engine and the same limits.

What about Chrome or Firefox on iPhone?

They work the same, because underneath they are the same browser. Apple requires every browser shipped for iOS to use WebKit, the Safari engine, and what changes between them is the interface, the sync and the address bar, not what a page is able to do.

This nearly changed. The Digital Markets Act forced Apple to open up alternative engines in the European Union, and BrowserEngineKit has existed since March 2024. More than two years later, on 18 June 2026, there was still no shipped browser with its own engine on iOS: Google, Mozilla and Microsoft have prototypes with Blink and with Gecko, and none has been released to the public.

The practical consequence for you: everything this page says about Safari applies to Chrome, Firefox, Edge and any other iPhone browser. Switching browsers on iPhone gets you around none of the limits below.

What changes between Safari on iOS and a desktop browser?

The costly line is the second. Safari on iOS caps the total memory used by drawing canvases, and when that budget runs out there is no loud error: subsequent canvases come back transparent and the operation produces blank pages. It is a limit that does not exist in Chrome or Firefox on a computer.

Which tools give trouble on iPhone, and why?

Many of the thirty-three draw nothing: they only manipulate document structure. Those behave on iPhone exactly as on a computer, and that is where the phone loses nothing.

Compress is the one that stalls first, and you can work out when. One A4 page drawn at the light level takes 8,022,576 bytes of canvas, which inside a 384 MB budget is around fifty pages. At the medium level it is around ninety, and at the strong level around a hundred and sixty five. Those are orders of magnitude and not guarantees, because Safari does not release canvases immediately after they stop being used, but they tell you where the border is: a ten page document compresses without drama, a three hundred page one does not.

There is also a per page limit, and that one catches posters. Safari refuses to draw a canvas larger than 16,777,216 pixels. An A0 poster at the medium level needs 18,077,306 pixels and comes out blank; at the strong level it needs 9,720,908 and passes.

Does signing a PDF with a finger work?

It does. The area where the signature is drawn listens to pointer events, the API that treats mouse, finger and stylus the same way, and Safari on iOS supports it. Page scrolling is switched off over that area, so dragging a finger draws instead of scrolling the page.

In practice, signing by finger on a phone gives a better stroke than signing with a mouse on a computer. The other two modes, typing your name and uploading a signature image, work too.

One limitation that is not an iPhone one but is worth repeating here: the signature is visual. It is a drawing placed on the page, not a qualified electronic signature, and it is no good where the law requires a certificate.

Where does the file go after downloading?

Into the Files app. Once the tool finishes, a download link appears on the page and you tap it; Safari handles it through its download manager and saves the result at whatever destination is set in Settings, Safari, Downloads, which by default is usually iCloud Drive and can be changed to "On My iPhone".

One detail of our implementation helps here: the tools do not download on their own. They produce a link that you tap, and a download started by your own tap is exactly the case Safari on iOS accepts without hesitation. The only exception is the sign tool, which fires the download right after applying the signature.

In PDF to image you get one link per page. On a twenty page document that is twenty links and twenty taps, which is tedious on a phone. We do not bundle the images into a compressed archive, and that is a shortcoming of ours.

Do iPhone photos go into a PDF properly?

They do, with a warning about size. The images to PDF tool embeds JPEG and PNG photographs exactly as they are, without re-encoding, and that is the best case: quality intact and size predictable.

Any other format is first redrawn and saved as PNG, which loses no quality but also does not compress photographs. The iPhone saves photos in HEIC by default, and that is precisely the case that falls into this branch: the final PDF can end up several times larger than the sum of the original photos.

If that matters to you, there are two ways out. The first is to change the camera format in Settings, Camera, Formats, choosing "Most Compatible", which switches recording to JPEG. The second is to share the photos to yourself in a way that converts them to JPEG before you pick them.

Can I install it on the Home Screen and use it offline?

You can. In Safari, tap the share button and choose "Add to Home Screen". The icon opens the app straight into full screen, with no address bar, because the site declares itself an installable app and points its start URL at the tools page.

After the first visit, the tools work with no internet connection: a service worker caches the app page, the stylesheet and the three PDF libraries that do the work. It is useful on a plane and anywhere with poor signal, and it is a direct consequence of processing being local.

What does not work well on iPhone?

• Compressing long documents. The 384 MB budget is the tightest limit of them all. Split the document first, or do it on a computer.
• A0 posters at the light and medium levels, which exceed the maximum canvas area and come out blank.
• Long operations look like faults. The drawing part runs on the main thread, so the page stops responding and there is no cancel button and no per page progress bar. On a phone that lasts longer.
• If iOS kills the tab for lack of memory, the page reloads and the work in progress is lost. The original file is intact, because it was never modified and never uploaded.
• There is no native app on the App Store. What exists is the site, which can be added to the Home Screen.
• OCR runs on the device's own processor, iPhone included, and it is the heaviest thing here. On a phone it takes time, and on a long document it may not finish. A scan of a few pages is fine; a whole archive is better done on a computer.

Sources

• Apple, using alternative browser engines in the European Union
• Open Web Advocacy, Apple browser engine ban persists under the DMA
• WebKit, limite de memória total de canvas (bug 195325)
• MDN, Pointer events