Quick start: compress a PDF for Ashby in under 2 minutes

If your real goal is simply make this PDF smaller so the Ashby upload goes through cleanly, this workflow is usually enough:

  1. Open Compress PDF.
  2. Upload the final resume, CV, cover letter, transcript, certificate, portfolio, or supporting PDF you actually plan to submit.
  3. Choose Medium compression first.
  4. Download the smaller result and compare the new size with the original.
  5. Open it once and check the details that matter most: your name, contact info, section headings, dates, bullet points, links, and any fine text inside certificates or work samples.
  6. If the file is still heavier than you want, use Extract Pages, Delete Pages, or Crop PDF before trying stronger compression.
Best default for Ashby: start with Medium compression. It usually gives the best balance between a lighter file and an application document that still feels polished when a recruiter opens it later.

Why smaller PDFs help in Ashby workflows

Ashby is often used in fast-moving hiring processes where candidates upload documents, revise them, and sometimes replace them across multiple applications. In that kind of workflow, oversized PDFs create the wrong kind of friction. They take longer to upload, feel clumsier to revise, and make routine document handling more annoying than it needs to be.

Smaller PDFs help in two useful ways. First, they move more smoothly through the application flow itself. Second, they make it easier to tell whether the real problem was file bulk or poor source quality. If a mostly text-based resume is still unusually large, the source often contains unnecessary graphics, screenshots, scanner borders, or extra pages that never improved the application in the first place. Compression lowers the weight, but it also exposes when cleanup is the smarter fix.

Why compression usually helps

  • Faster uploads: useful when you are applying on normal Wi-Fi, mobile data, or a laptop you just want to use quickly.
  • Less replacement friction: smaller files are easier to swap out when you tailor a resume or update a supporting document.
  • Cleaner recruiter previews: lean PDFs open faster and feel more intentional than bloated scans or messy exports.
  • Better reuse across portals: if a file behaves well in Ashby, it usually behaves well when emailed directly or uploaded to another ATS later.

The file does not need to be tiny at all costs. It needs to be light enough to move easily while still keeping the information that matters readable without zooming, guessing, or second-guessing the document.

What file size should you aim for?

There is no single universal Ashby size rule that applies to every employer setup, so the goal is not to chase a magic number. The better approach is to make the file comfortably light while preserving the parts that must still look trustworthy. For most candidate-facing PDFs, that means optimizing for the smallest useful version rather than the smallest possible version.

Document type Practical target What matters most
Resume or CV Usually under 2MB Clear headings, dates, bullets, contact info, and links
Cover letter Usually well under 2MB Stable spacing, readable body text, and a clean signature area
Transcript or certificate Often 2MB to 5MB Legible rows, seals, dates, and small labels
Portfolio or work sample PDF Often 2MB to 5MB Readable captions, charts, screenshots, and layout integrity

Those are not hard limits. They are working targets that usually make uploads and previews smoother without turning the document into something fuzzy, stripped-down, or visually careless.

Good rule of thumb: for resumes and cover letters, lighter is usually better as long as the text still feels crisp. For scanned proof or image-heavy samples, prioritize trustworthiness over aggressively forcing the file below a number that the reader will never notice.

Which compression level should you choose?

Most people should not start by asking, What is the strongest compression I can get away with? A better question is, What is the lowest-risk compression that still makes the file meaningfully smaller? For Ashby, that answer is usually Medium.

Why Medium is usually the best starting point

Medium compression normally gives the best tradeoff for application documents. It reduces the weight enough to matter while keeping names, headings, dates, body text, links, and smaller supporting details readable. That matters because recruiters do not just need the file to upload. They need it to open cleanly and still look like something a careful candidate prepared.

When Low compression makes sense

Low compression is useful when visual sharpness matters more than squeezing out every megabyte. That includes polished portfolio pages, certification proofs with fine lines, or work samples where small charts and screenshots still need to feel crisp. If the file is already near your target, Low may be enough.

Use stronger compression only after cleanup

High compression can help when the file is still too large, but it is also where quality problems show up first. Thin text, small labels, seals, and screenshot details can soften quickly. That is why stronger compression should usually come after page cleanup, not before it.

Good operating order: compress first, review second, trim or split third, then use stronger compression only if the cleaned-up file is still bulkier than the Ashby workflow really needs.

Step-by-step: shrink an Ashby PDF with LifetimePDF

  1. Start with the final shareable version. Remove obvious draft pages before you compress anything.
  2. Open Compress PDF. Upload the resume, CV, cover letter, transcript, certificate, portfolio, or supporting file you actually plan to send.
  3. Choose Medium compression. That is the safest default for most Ashby uploads.
  4. Download the smaller copy. Compare the size so you know whether the change was meaningful.
  5. Do a recruiter-and-parser pass. Check names, dates, bullets, hyperlinks, section headings, transcript text, and any small labels inside a certificate or work sample.
  6. Clean the structure if needed. Use Extract Pages, Delete Pages, or Crop PDF to remove weight that does not help the next reader.
  7. Keep the right version. Your archive copy can stay fuller if needed; the Ashby-facing copy should be lean, readable, and easy to upload.

The biggest mistake is treating every application like it needs one giant all-in-one PDF. Usually it does not. A smaller file with the right pages is better than a bloated packet that tries to do every job at once.

Best strategy for common Ashby file types

Resume or CV

A resume should usually compress well because it is mostly text. If it comes out strangely large, the file often contains unnecessary graphics, embedded screenshots, or messy export settings. Medium compression is normally enough, and a clean re-export from Word is often even better. Because Ashby workflows may parse the uploaded resume, it is worth prioritizing clean real text over decorative design tricks.

Cover letter

Cover letters should usually end up quite small. If yours is heavy, something hidden is probably bloating it. Compress it once, then confirm that spacing, line breaks, and any signature area still look intentional.

Transcript, certificate, or scanned proof

These often behave more like image files than text files. That means they can stay bulky even when they do not look complicated. Clean borders, remove blank pages, and crop scanner waste before you push compression harder. If you also want searchable text, run OCR PDF on the cleaned version.

Portfolio or work samples

These are the hardest files to optimize because visual quality matters. Start with Low or Medium compression, then decide whether every page truly belongs in the application. A shorter, stronger portfolio usually works better than a larger one that feels technically impressive but harder to upload.

Best practical habit: keep one version for the application workflow and another for your personal archive. The lighter working copy can stay focused, while the fuller version keeps extra backup context available when you need it.

What if the PDF is still too large?

If Medium compression does not bring the file down far enough, do not jump straight to the harshest setting. Ashby PDFs usually get smaller faster when you remove unnecessary pages and repeated visual baggage first.

Try these fixes before pushing compression harder

  • Extract only the pages the employer or recruiter needs: many applications do not need the full packet.
  • Delete duplicate pages: repeated scans, covers, or duplicate proofs add size quickly.
  • Crop wasted margins: scanner borders and oversized white space add weight without adding meaning.
  • Split large combined documents: if the workflow offers separate upload fields, use them instead of forcing everything into one file.
  • Rebuild a messy source file: if the original PDF is bad, re-exporting cleanly can work better than repeated compression passes.

If you still need a smaller file after that, then try a stronger compression pass. But do it on the cleaned-up version, not the original oversized packet. That is usually how you get a better result without sacrificing readability too aggressively.

How to keep Ashby files readable and parser-friendly

People worry that compression will break resume parsing, but the bigger risk usually comes from the source file. If your PDF is built from screenshots, scans, or heavily decorative layouts, the problem started before compression did. Clean text, stable headings, readable dates, and sensible formatting matter more than chasing the smallest possible file.

Check these before you upload the compressed file

  • Your name, phone number, email, and location line
  • Section headings and bullet alignment
  • Job titles, dates, and employer names
  • Links to portfolios, LinkedIn, GitHub, or project pages
  • Small transcript text, certificate details, signatures, or seals
Simple test: open the compressed copy at normal zoom and scroll as if you were the recruiter seeing it for the first time. If it still feels easy to trust without constant zooming, the PDF is probably in good shape.

Privacy and document-cleanup habits before you upload

File size is only part of the story. Application documents can also carry hidden details you may not want to send everywhere: metadata, extra pages, comments, or identifiers that do not belong in the final upload.

Before uploading, it is worth taking a quick privacy pass. If the PDF includes an unnecessary address, comments, old revisions, or pages the employer never asked for, clean those first. If you want to review hidden document properties, use PDF Metadata Editor. If a supporting file includes sensitive personal details, use Redact PDF before submission.

If you want a safer archive copy after applying, you can also lock your stored version with PDF Protect. That step is for your own records, not the Ashby upload itself.

If you work with Ashby uploads regularly, these tools usually pair well with compression:

  • Compress PDF for the first size-reduction pass
  • Word to PDF for cleaner resume exports
  • Extract Pages for smaller application-friendly subsets
  • Delete Pages for duplicate scans, blank pages, and irrelevant extras
  • Crop PDF for scanner borders and wasted margins
  • OCR PDF when a cleaned scan also needs searchable text
  • Redact PDF for removing details the employer does not need

These related guides may also help if you want companion coverage around the same workflow:

Bottom line: for most Ashby uploads, start with Medium compression, review readability once, and trim page weight before using stronger compression.

Compress a PDF for Ashby Review PDF Metadata Get Lifetime Access

FAQ (People Also Ask)

How do I compress a PDF for Ashby?

Upload the PDF to a compressor, start with Medium compression, and keep the smaller copy only if names, headings, dates, body text, links, and contact details still look clear. Medium compression is usually the safest first pass because it reduces size without making the application look careless.

What PDF size should I aim for in Ashby?

Under 2MB works well for resumes and cover letters. Scan-heavy transcripts, certificates, or portfolios can land higher, but staying around 2MB to 5MB usually makes uploads and previews smoother without creating unnecessary friction.

Will compression hurt resume parsing in Ashby?

Usually not if you start with Medium compression and the source file already contains real selectable text. The bigger risk is a PDF built from screenshots, scans, or overly decorative layouts instead of clean text-based pages.

Should I upload one combined PDF or separate files in Ashby?

Only if the application flow truly expects one file. If the Ashby workflow provides separate upload fields, keeping files separate is usually cleaner than creating one oversized combined packet.

Which LifetimePDF tools pair best with Ashby uploads?

Compress PDF is the main starting point. Word to PDF, Extract Pages, Delete Pages, Crop PDF, OCR PDF, Redact PDF, and PDF Metadata Editor are all useful when you want smaller, cleaner application files without oversharing extra pages or hidden metadata.