Free · Fast · Privacy-first

Convert Screenshots to PDF

A folder of screenshots is hard to send and harder to read in order.

⚡

One PDF, many screenshots

🔒

Lossless quality preserved

✨

Drag to reorder

⚡

No upload, no watermark

Cost: Free tier
Sign-up: Not required
Processing: Tool-specific
Privacy: Clearly disclosed

FreeNo signupWhite-label

Add this Image to PDF to your website

Drop the Image to PDF into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/pdf/image-to-pdf?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image to PDF by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/pdf/image-to-pdf?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image to PDF by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Why convert screenshots to PDF instead of just sending the image folder

A folder full of screenshots is a poor delivery format for several reasons that compound the larger the folder gets. Reviewers cannot scroll through a folder the way they scroll through a document, so they end up double clicking each file in sequence, which is friction that erodes the careful order you arranged the files in. Filenames such as Screenshot 2024-05-14 at 11.32.07.png contain no context about what is in the image, so anyone receiving the folder has to open each file to know what they are looking at. Email gateways often choke on attachments numbering more than twenty, so the folder ends up split across multiple emails or zipped into an attachment that recipients have to extract before they can see anything. A single PDF avoids all of these problems: it is one file, the pages are in the order you set, and the reader scrolls through them naturally like any other document.

PDF is specifically the right container for screenshot collections because it preserves the visual layer without imposing any structure on the content. Word documents would force you to embed each image into a page with whatever formatting Word imposes, often shrinking or wrapping images in unexpected ways. PowerPoint would let you put one image per slide but the result is harder to scroll than a PDF. HTML would work but requires hosting and reduces portability. PDF is the universal standard for fixed layout visual documents and every device has a reader that opens it cleanly without any compatibility friction.

FixTools converts a batch of screenshots to PDF using a fully client side pipeline. When you drop a folder of screenshots onto the upload area, the browser reads each PNG, JPG, or HEIC into memory in turn. The tool extracts dimensions from each image header, sorts them by filename alphabetically (which works perfectly for the default OS naming pattern Screenshot YYYY-MM-DD), shows you thumbnail previews that you can drag to reorder if the alphabetical order is wrong, and then assembles a multi page PDF with one screenshot per page. Each page is sized to A4, US Letter, or fit-to-image depending on your preference. The PDF is built in memory and offered as a download once complete.

The lossless preservation property matters for screenshots in particular because screenshots almost always contain text or sharp UI elements that JPG compression would damage visibly. Screenshots saved as PNG use lossless compression internally, and FixTools embeds the PNG bytestream into the PDF using FlateDecode (the PDF equivalent of PNG's DEFLATE compression), preserving every pixel exactly. The result is a PDF that prints crisp at any zoom level, with terminal output remaining readable, dashboard graphs remaining sharp, and font edges remaining clean. This is the right output for any workflow where the reviewer needs to read the content of the screenshots, not just glance at them.

PNG specification (W3C)PDF specification (Adobe open source)macOS screenshot file format docs (Apple)

How to use this tool

💡

Drop a folder of screenshots onto FixTools. The tool sorts them by name, lets you reorder via drag and drop, and produces one PDF with one screenshot per page.

How It Works

Step-by-step guide to convert screenshots to pdf:

1
Capture your screenshots
Take the screenshots you need using your operating system's capture tool. On Mac use Cmd Shift 4 for a selected area or Cmd Shift 3 for the full screen. On Windows use Win Shift S for snipping or PrtScn for the full screen. On Chromebook use Ctrl Shift Show-Windows. Each captured image is saved as a PNG to your screenshots folder with a timestamped filename.
2
Drop them into FixTools
Open the FixTools Image to PDF page. Select all your screenshots in Finder or Explorer and drag them onto the upload zone in one go. The tool sorts them alphabetically by default, which matches the timestamped naming pattern so the chronological order is preserved automatically.
3
Reorder if needed
Drag thumbnails up or down in the preview list to change the order. This matters if you captured screenshots out of sequence, or if you want to insert a separator or rearrange to match the narrative of a bug report or tutorial. Removing a screenshot from the batch is a single click on its thumbnail.
4
Generate the PDF
Click Convert to PDF. The tool assembles every screenshot into a multi-page PDF in seconds and triggers the save dialog. Name the file something descriptive (such as bug-report-checkout-flow.pdf or tutorial-new-user-onboarding.pdf) and save it locally.

Real-world examples

Common situations where this approach makes a real difference:

QA engineer filing a detailed bug report

A QA engineer reproduces a bug in a checkout flow across eight screens: the product page, the cart, the address entry, the payment screen, and several intermediate error states. They take a screenshot at each step, drag the resulting eight PNGs into FixTools, generate a single PDF, and attach it to the JIRA ticket. The developer who picks up the ticket can scroll through the entire reproduction sequence in one document instead of clicking through eight individual image attachments, drastically reducing the time it takes to understand the bug.

IT support documenting a new procedure

An IT manager writes a procedure for new employees on how to enrol their corporate phone in MDM. They take twenty four screenshots across an iPhone and a MacBook, drop them into FixTools in the order they should be performed, and produce a PDF tutorial they can attach to the onboarding email template. Each new hire receives the same scrollable PDF the night before their start date and arrives on day one already familiar with the procedure they will perform with the IT desk.

Researcher capturing browser-based evidence

An academic researcher studying online discourse captures forty screenshots of social media threads over a one hour observation session, using a browser screenshot extension that saves each as a timestamped PNG. They convert the lot into a single PDF using FixTools and archive the PDF in their research drive. The PDF preserves the visual evidence chronologically, can be cited as a single archival object in the paper, and lasts longer than the social media threads themselves which may be deleted or edited later.

Manager preparing a board pack

A founder preparing for a quarterly board meeting captures fifteen screenshots from internal analytics dashboards, customer support tools, and product mockups. They combine them into a single PDF appendix to the board deck through FixTools in five minutes, attach the PDF to the board email along with the main deck, and the directors receive a single coherent appendix instead of fifteen loose images that would have been ignored in their inbox.

Pro tips

Get better results with these expert suggestions:

Use timestamped filenames to preserve order automatically

OS screenshot tools name files with timestamps by default, which sort correctly alphabetically. Resist the temptation to rename screenshots immediately after capture: the default names are perfect for batch conversion. Rename only after the PDF is generated if you want a more descriptive filename for the final document.

Annotate before converting if context is needed

If your screenshots need callouts (red boxes around the broken element, arrows pointing at the wrong button), annotate them in your OS screenshot tool or in Skitch or Preview before dropping them into FixTools. The PDF embeds the annotated images, so callouts come along automatically. Adding callouts after the PDF is generated requires PDF annotation tools and is more friction than adding them at capture time.

Capture at 2x or retina resolution for print clarity

Modern Mac and PC screenshots are captured at native pixel resolution, which is roughly 2x on retina displays. If your PDF will be printed or projected, the 2x density ensures the result remains crisp. Avoid scaling screenshots down before adding them to the PDF: smaller source pixels mean a fuzzier print.

Add a cover or title page if you control the order

For tutorials and reports, capture a final screenshot with a clearly labeled title (using your OS screenshot annotation or a quick Keynote/PowerPoint slide exported as PNG) and drop it first in the batch. The result is a PDF with a proper cover page that frames the rest of the screenshots for the reader.

FAQ

Frequently asked questions

No enforced limit. The practical limit is browser memory: a typical laptop handles batches of fifty to a hundred screenshots comfortably. For larger batches such as a documentation project with several hundred screenshots, split into two or three batches and combine the resulting PDFs using the FixTools PDF Merger. Most real bug reports and tutorials fall under fifty screenshots, well within the comfortable single batch range.

Yes, pixel for pixel. The tool embeds screenshot pixel data into the PDF using FlateDecode (lossless) compression, so what you saw on screen when you captured the image is exactly what appears in the PDF. There is no compression artifacting, no color shift, and no resizing unless you set a page size that requires scaling. For pixel accurate output, use fit-to-image page size which sizes each page to match its source screenshot.

The FixTools converter itself does not add annotations. For annotations, either annotate the screenshots in your OS tool before converting, or open the resulting PDF in Preview (Mac), Adobe Acrobat Reader, or any PDF annotation tool to add callouts and notes after conversion. The PDF is a standard ISO 32000 document and works with every PDF annotation app.

Yes. Mac screenshots are saved as PNG by default. Windows screenshots are PNG when saved through the Snipping Tool or PrtScn. ChromeOS screenshots are PNG. All three are handled identically by the tool because PNG is PNG regardless of the OS that produced it. iPhone screenshots are also PNG when AirDropped to a Mac or PC, and HEIC when accessed through the iCloud Photos library, both of which are supported.

The default order is alphabetical by filename. If your filenames do not sort in your desired order (for example img-10.png sorts before img-2.png because lexicographic ordering treats them character by character), rename the files with zero padding (img-002.png, img-010.png) or drag the thumbnails in the FixTools preview to manually reorder before generating the PDF.

Yes. Drop the same file twice into the upload area, or duplicate a file with a different name and drop both versions. The tool treats each upload as a separate page. This is useful for tutorials where you want to refer back to an earlier screen at a later point in the narrative without making the reader scroll backward.

No, not from raw screenshots. Screenshots are raster images and the text inside them is pixel data, not searchable text. The resulting PDF contains no OCR layer. If you need a searchable PDF from screenshots, run the output through an OCR tool such as Adobe Acrobat Pro's recognise text feature, or use a dedicated OCR converter, before archiving. FixTools focuses on the conversion step; OCR is a separate workflow.