You found the right URL, but the PDF looks soft, cropped, or nothing like the live site. Nine times out of ten the fix is not a different website: it is a PDF conversion option you have not matched to the job. This field guide explains what each major setting does when you turn a webpage or HTML into a PDF, how quality and page size interact, and when watermarks, headers, footers, or color overlays earn their place. By the end you should be able to open any converter, pick settings with intent, and know what to change when the first export disappoints you.
We will reference the same kinds of controls you see in our URL to PDF converter and related flows. If you are new to the topic, skim How to Convert Website to PDF first for methods and mindset, then use this article as your pdf settings cheat sheet. For a shorter workflow focus, Master PDF Generation: Convert URLs Like a Pro pairs well with the detail below.
Read this before you touch a single toggle
Web PDF export is render-then-paginate: the tool loads the page (or HTML), applies CSS, runs scripts as needed, then slices the result into pages. PDF conversion parameters such as quality and viewport size change that render, not magic post-processing. That is why “High” quality cannot fix a layout that was captured at the wrong width, and why a mobile viewport can make a desktop dashboard unreadable.
Work in this order when you can: (1) page format or viewport, (2) quality, (3) optional branding (watermark, header, footer, color layer). Swapping steps one and two wastes time because format shifts line breaks and images more than bitrate does.
Quality: Low (30), Medium (75), High (100)
Quality controls how aggressively visual detail is compressed when the engine rasterizes parts of the page. It hits file size and sharpness of photos, gradients, and fine UI chrome more than it changes plain body text.
- Low (30): Use for long text articles, internal notes, and attachments where megabytes matter. Expect softer screenshots and hero images; paragraphs usually stay fine.
- Medium (75): The best default for most website to PDF jobs: reports, blog saves, marketing pages, and handouts. You get readable type and acceptable imagery without oversized files.
- High (100): Reserve for design reviews, maps, data visualizations, and anything that will be zoomed or printed with photos. File size jumps; that is normal.
Quick check: if your PDF is huge but mostly text, try Medium or a narrower desktop format before you blame the tool. If logos look fuzzy at Medium on a retina-heavy page, bump quality before you chase other settings.
Page format: why width beats “paper” unless you print
Format sets the virtual screen size before pagination. Match it to how the page is meant to be viewed, not to your personal monitor.
Mobile presets
Examples include iPhone SE (375×667), iPhone 12/13 (390×844), iPhone 11 Pro Max (414×896), Android small (360×640) and large (412×915). Choose these for mobile-first sites, store listings, or QA evidence that a breakpoint looks correct.
Tablet presets
iPad (768×1024), iPad Air (810×1080), iPad Pro 11-inch (834×1194), iPad Pro 12.9-inch (1024×1366) suit e-learning, tablet sales decks, and design sign-off where the iPad is the reference device.
Desktop and laptop
From laptop small 1366×768 through Full HD 1920×1080. This is the right cluster for SaaS apps, marketing homepages, and “what the team sees in Chrome” archives. When unsure, start near laptop medium 1440×900 and adjust if columns feel cramped or too wide.
A4 and Letter
A4 (794×1123) and Letter (816×1056) align pagination with real paper. Prefer them when someone will print or when you want conservative page breaks for formal packets.
Watermarks: short text, high signal
Watermarks add diagonal or repeated text over the page for status and ownership. Typical controls include text (often up to a modest character limit), color, and visibility. Good uses: DRAFT, CONFIDENTIAL, client name, or copyright. Bad uses: long sentences that fight the underlying layout.
Turn watermarks on when PDFs leave your Slack or email and could be forwarded without context. Keep wording short so it reads in one glance.
Headers and footers: make every page self-explanatory
Headers sit at the top of each printed page, footers at the bottom. Many tools let you set text and color separately for each. Strong combinations include title in the header and capture date plus source URL in the footer. That single habit prevents “which site is this from?” confusion a week later.
Treat the character limits as a feature: they force you to write labels, not paragraphs. Match color contrast to the page so lines stay legible on both light and dark sections.
Color layer (overlay): brand tint with a light hand
A color layer applies a semi-transparent wash across the whole PDF. It can unify training packs under one brand hue or visually separate “snapshot” PDFs from live site content. Push opacity too high and you sacrifice readability, so preview on a dense page before you commit.
PDF output versus image output
When the product offers PDF, you get multipage documents, selectable text in many cases, and a format built for sharing and print. When you switch to image export (PNG, JPEG, WebP) in tools like our Web to Image flow, you trade multipage structure for a single raster or per-page images. Use PDF for archives and handoffs; use images for thumbnails, Slack previews, or strict pixel snapshots.
Working from pasted markup instead of a URL? HTML to PDF online uses the same quality and format ideas; only the input source changes.
When the PDF looks wrong: a five-point checklist
- Wrong width: Try the next desktop size up or down, or switch to mobile if the site is responsive and you chose a huge viewport.
- Missing images: Lazy-loaded media may need more time on the server; retry, or check FAQs for wait and login options if the page is protected.
- Cut-off content: Long pages may need full-page or dedicated long-scroll handling depending on the tool; confirm you are not using a print-style clip.
- Blurry everything: Raise quality one step before you change format.
- Odd colors: Disable color overlay experiments; then retest. Some sites use dark mode or filters that interact badly with overlays.
Common mistakes people repeat
- Always using High quality: Wastes space on text-only exports.
- Picking paper size for screen-only PDFs: Can reflow responsive sites in ways you did not expect.
- Skipping a one-page test: Batch jobs multiply a bad preset across every URL.
- Heavy watermark plus loud header plus color layer: Legibility drops fast; add effects one at a time.
- Forgetting the source in the footer: Future you will not remember which build of the site you captured.
Putting it together: a minimal repeatable recipe
- Paste the URL into the PDF tool (or your HTML into the HTML flow).
- Select format: mobile, tablet, desktop, or A4/Letter based on audience.
- Set quality to Medium; raise to High only if visuals look soft.
- Add footer text with date and URL if the file leaves your machine.
- Add watermark only if status or confidentiality matters.
- Download, scroll the last page, then adjust format or quality if needed.
Conclusion
PDF configuration is less about memorizing every pixel size and more about pairing viewport, quality, and optional branding with how the file will be read. Treat pdf conversion options as a small checklist each time, run one test export before bulk work, and use headers or footers so every page carries context. With that discipline, you spend less time re-exporting and more time using the PDF you already have.
