Question 1

Does Bind upload my files to a server?

Accepted Answer

No. Conversion runs inside this browser tab with pdf-lib, pdf.js and the Canvas API. Images and PDFs are never posted to Bind’s hosting, never stored in a cloud bucket, and never sent to a conversion API. If you disconnect after the page has loaded, the converter still works. That is the point of a private tool: a scan of a passport, a medical form or a lease can become a PDF without leaving the device that photographed it.

Question 2

Do I need an account or a daily limit?

Accepted Answer

No account, no email gate, no watermark, no artificial cap on how many files you convert. The only ceiling is the memory of the browser you are using. A recent phone handles a few dozen photos without drama. A 200-page PDF at 3× scale on an older iPad may stall — lower the scale or split the range. We do not throttle successful jobs to sell a paid plan.

Question 3

Which image formats can I turn into a PDF?

Accepted Answer

JPEG, JPG, PNG, WebP, BMP and static GIF. Drop them in any mix, reorder the list, then bind. HEIC and HEIF from iPhone Camera are not decoded here — convert those with HEIC Local first, then bring the JPEG or PNG into Bind. Animated GIF uses the first frame only. Vector SVG is out of scope; Bind builds raster pages, not a drawing editor.

Question 4

How do page size, margins and Contain / Cover / Stretch work?

Accepted Answer

Page size is the paper you are targeting: A4, Letter, Legal or a square. Margins keep photos off the edge for printing. Contain fits the whole image inside the content box and may letterbox. Cover fills the box and may crop overflow. Stretch fills the box and may distort. For a scan of a document, use Contain plus modest margins. For a full-bleed photo sheet, use Cover. Stretch is a last resort when you explicitly want the image to match the page regardless of aspect ratio.

Question 5

Can I extract only some pages from a PDF?

Accepted Answer

Yes. Leave the control on all pages, or type a range such as 1-3,5,8-10. Spaces are ignored. Out-of-range numbers are dropped rather than crashing the job. Each selected page is rasterized at the scale you pick (1×, 2× or 3×) and saved as PNG, JPEG or WebP. Download one page or a ZIP of the set. Encrypted or broken PDFs surface an error instead of a blank ZIP.

Question 6

PNG, JPEG or WebP — which should I export?

Accepted Answer

PNG is lossless and the right default for text, UI screenshots, stamps and signatures. JPEG is smaller and fine for photographs; pick a quality that still reads. WebP is usually smaller than JPEG at similar visual quality and works in modern browsers and many CMS pipelines, but some print shops still want JPEG or PNG. Scale multiplies pixels: 2× of an A4 page is already a large PNG. Start at 2× PNG for documents you will OCR later; drop to 1× JPEG for a quick preview pack.

Question 7

Why does a page look softer than the original PDF?

Accepted Answer

A PDF page is often vectors and fonts. Bind rasterizes that page into pixels. At 1× the pixel grid may be too coarse for small type. Raise scale to 2× or 3×, export PNG, and avoid stretching. Scanned PDFs that are already bitmaps cannot gain detail Bind never had — you only choose how large to paint the existing bitmap. If a font looks wrong, the file may use a subsetted font pdf.js cannot reconstruct; try a different PDF export from the original app.

Question 8

Does Bind work on iPhone and iPad?

Accepted Answer

Yes. Safari on iOS is a supported path for both directions. Use the file picker or Files app, then Bind or extract. After a PDF is ready, the share sheet can hand it to Mail, Files or another app when the browser exposes Web Share. Very large batches still hit Safari memory first — convert in groups of 10–20 photos rather than 200 at once. Add to Home Screen if you want the tool as an icon; it remains a website, not a native App Store binary.

Question 9

Is there a file-size limit?

Accepted Answer

Bind does not impose a product quota. The browser does. A warning appears around 80 MB of source bytes because heaps above that often fail on phones. A 40-megapixel photo is heavier than it looks. If the tab reloads or the job dies, reduce count, shrink images first, or extract a narrower page range. Desktop Chrome usually survives larger jobs than mobile Safari. Nothing is queued on a server when a job fails — there is no server job.

Question 10

Can I reorder images before making the PDF?

Accepted Answer

Yes. Drag rows on a pointer device. On a phone use the up and down controls on each row. The PDF page order matches the list, top to bottom. Filenames are sanitized for download but do not change page order. Duplicate a photo in the list if you need it twice; remove a row if it was added by mistake. Clearing the list revokes object URLs so the tab does not keep thumbnails in memory.

Question 11

How is Bind different from Folio, Fit or a cloud converter?

Accepted Answer

Folio splits, compresses and (where enabled) merges PDFs — it does not turn a folder of JPEGs into a new document. Fit resizes and crops raster images for the web. Bind’s job is the hinge between photos and pages: images become a multipage PDF, and PDF pages become images. Cloud converters upload bytes to a farm. Bind never does. If you need OCR, electronic signatures or form filling, use a dedicated editor after Bind has produced the file; those features are intentionally out of scope.

Question 12

Will my PDF open in Acrobat, Preview and a printer?

Accepted Answer

Bind writes a straightforward PDF with one raster image per page, sized to the paper you chose. Acrobat, Apple Preview, Chrome, most printers and most government upload portals accept that pattern. We do not embed JavaScript, attachments or PDF/A archival profiles. If a portal rejects the file, it is usually because of an encryption or PDF/A rule on their side — print-to-PDF from the preview, or ask them which profile they require. Colors follow the source image, not a CMYK press profile.

Question 13

Who operates Bind and how do I get support?

Accepted Answer

Bind is a free utility from Ultimatum. There is no ticket portal and no guaranteed SLA — it is a browser page, not a hosted conversion API. For a broken page, a policy question or a copyright notice, email ultaultimatum@gmail.com from the Contact page. Do not attach passports or medical scans to that email; if the converter failed, describe the browser, page count and the error text instead of sending the file.

Question 14

Will the bound PDF appear in my iPhone Photos album?

Accepted Answer

No. Photos is for stills and Live Photos. A PDF is a Files object. After Bind, save into Files or iCloud Drive. Recents in Photos still holds the original JPEGs, not the document you just made.

Question 15

If I send the pages as WhatsApp photos, is that the same as sending the PDF?

Accepted Answer

No. Photo send recodes frames. Page 2–12 may never leave as a document. Send the PDF as a document if the other person must keep the page order. Bind does not sit inside WhatsApp.

Question 16

Should I email the PDF or the ZIP of extracted pages?

Accepted Answer

Email the PDF when the recipient asked for a document. Email extracted JPEGs only when a portal demands “JPG of page 3”. A 3× PNG ZIP of a long report will blow past Gmail’s 25 MB attachment cap and become a Drive link.

Question 17

Does Bind merge two PDFs or strip GPS from the photos?

Accepted Answer

No. Merge/split/compress is a different tool. GPS/EXIF is a different tool. Bind’s job is pages from pictures and pictures from pages in this tab.

Talk to a human

What to include

What not to send