TL;DR
PayPal announced plans to eliminate about 20% of its 23,800-person workforce over the next two to three years — roughly 4,760 jobs — joining Meta (8,000), Cloudflare (1,100), Coinbase (700), and Oracle (30,000+) in a 2026 layoff wave that hit nearly 38,000 US tech workers in the first 10 days of May alone. If you're inside that 4,760, the paperwork load is large and the privacy stakes are high. Convert: Anything to PDF converts every document type you'll receive — DOCX separation agreements, XLSX severance worksheets, image scans of badges and IDs, HTML emails — into clean PDFs without uploading any of it to a third-party service.
What we know about PayPal's plan
The publicly disclosed shape:
- ~20% of 23,800 employees — about 4,760 positions to be eliminated
- Timeline: 2-3 years, not a single-day announcement like Meta's May 20 wave
- Driver: AI-led restructuring and cost discipline, consistent with the broader pattern (47.9% of 2026 layoffs cited AI/automation as the reason)
- Affected areas: not yet itemized publicly; expected to include parts of fintech engineering, sales operations, fraud, and middle-management layers
A multi-year layoff is structurally different from a one-day wave. You may not know until the second or third tranche whether you're affected, which changes how you plan: documentation is something you build during the rolling reductions, not in a single day.
What "documentation" actually means in a multi-year rolling layoff
In a one-day wave (Meta, Cloudflare, Coinbase), you get one packet on the morning of, lose access by lunch, and spend a weekend organizing. In a 2–3 year rolling reduction, the pattern is:
- Reorgs every quarter with team-mapping documents
- Internal "talent marketplace" listings as roles open and close
- Performance calibration cycles with implications for stack-ranked layoffs
- Severance terms that may evolve between tranches
- Manager and skip-level changes affecting recommendation networks
- Equity vest schedules that interact with possible separation timing
- Internal communications announcing each round
If you're proactive, you save and archive material on a quarterly cadence. If you're not, by the time you're affected, half of what you wish you had is gone.
| Document type | When to save | Format you'll receive |
|---|---|---|
| Quarterly reorg announcements | Day of | HTML / Slack export |
| Performance reviews (yours) | At delivery | DOCX / PDF / HTML |
| Calibration grids (where visible) | Immediately | Screenshot / HTML |
| Severance term updates | When published | PDF / HTML |
| Internal job postings (your team) | Monthly | HTML |
| Manager 1:1 notes | Ongoing | Markdown / Docs |
| Recommendation letter drafts | Pre-emptively | DOCX |
| Equity vest schedule | Quarterly | Carta / Shareworks HTML |
| Benefits portal screenshots | At each enrollment | HTML / Screenshots |
| Recruiter conversations (external) | Per-thread | Email / HTML |
All of these are mixed-format. Convert: Anything to PDF handles every one of them, and importantly, does it locally — which matters when the documents contain SSN snippets, salary info, performance ratings, or comparator data.
Why a Chrome extension beats an online PDF tool for HR paperwork
The temptation in the moment is enormous: "I'll just upload this DOCX to SmallPDF / ILovePDF / Adobe online and get a PDF." Don't.
A separation document contains:
- Your full name, address, phone, often partial SSN
- Salary, equity grant amounts, bonus structure
- Severance dollar amount and waiver language tied to it
- Healthcare plan ID and enrollment numbers
- Performance ratings, comparator language, "non-discriminatory" statements
- Termination coding (relevant to unemployment claims)
- Bank routing info if direct deposit info was included
- Confidentiality and non-disparagement language with specific dollar penalties
Every byte of that goes through a third party's servers when you use an online PDF tool. Some retain content for "abuse prevention" indefinitely. Some pass content to advertising partners. Several have had documented breaches in 2023-2024. Even the ones with the cleanest privacy posture have logs, backups, and a security team you can't audit.
Convert: Anything to PDF does the conversion in the Chrome extension itself. The file is read from disk, processed in the extension's sandbox, and written back to disk as a PDF. No network involved.
A multi-year documentation workflow
If you work at PayPal (or any of the companies running multi-tranche reductions in 2026), here's a workflow that puts you in a strong position regardless of which round, if any, affects you.
Each month
- Save your performance dashboard as PDF if it's visible
- Capture any team-mapping or reorg announcements
- Update your "running résumé doc" with current quarter accomplishments — convert to PDF at month-end
Each quarter
- Save your equity vest schedule from Carta/Shareworks
- Capture the severance terms page (if disclosed internally) as PDF
- Update your portfolio PDFs with shipped work
- Run a recruiter-recruiter list: anyone who's reached out in the last 90 days, save the email threads as PDF
Each performance cycle
- Save your performance review as PDF (DOCX → PDF)
- Capture your calibration outcomes if available
- Save your goal-setting documents
If you're notified
- Treat it as a one-day wave from that moment: capture everything from your HR portal before access closes
- Convert all received documents to PDF
- Build the five-packet structure (severance, benefits, tax, unemployment, archive)
If you're not notified but the round happens
- Update your records of who left and who survived (for institutional memory and recommendation networks)
- Save the public press release as PDF
- Snapshot any internal communications you can capture
The cadence is light — maybe 20 minutes a month — and it leaves you with a complete, current archive whenever the news lands.
A note on formats you'll actually deal with
Here's a calibration on what conversion looks like for each common case:
| Source | Convert to PDF when... | Notes |
|---|---|---|
| DOCX separation agreement | Immediately on receipt | Preserve track-change history in source DOCX too |
| XLSX severance worksheet | Immediately on receipt | The PDF preserves values; keep XLSX for live calculations |
| HTML benefit enrollment portal | After completing enrollment | Capture both the form and the confirmation screen |
| Email threads (Outlook / Gmail) | Whenever a decision is documented | Save the entire thread, not just the latest reply |
| Carta / Shareworks vest schedule | Quarterly | Use full-page capture; tables span the fold |
| Internal Confluence / Notion pages | Before access closes | These vanish from your view immediately on separation |
| Slack message exports | If your company allows export | DM history is hard to reconstruct after the fact |
| Screenshots (PNG/JPG) | Anytime you can't get a "real" copy | Merge multiple screenshots into one PDF |
Convert: Anything to PDF handles all of these. Multi-file merge is one click — drag your DOCX, XLSX, PNGs, and existing PDFs in, choose an order, output one packet.
Building your five-packet structure
The same packet structure that works for a one-day wave works for a multi-year reduction — you just keep updating it as material accumulates.
- Negotiation packet — separation agreement (when received), severance worksheet, comparable role research, market salary data, lawyer notes
- Benefits continuation packet — COBRA forms, 401(k) options, HSA balance, dependent insurance schedules, equity acceleration tables
- Tax packet — pay stubs by quarter, equity vest disclosures, state withholding, year-end W-2 estimates
- Unemployment packet — termination notice (when received), last-pay-period stub, WARN notice if applicable, state forms
- Personal archive — performance reviews, project portfolios, public recommendation letters, recruiter threads, capability statements
Each packet is a folder of source files (DOCX, XLSX, HTML) and one merged PDF that you regenerate when material changes.
What about Cloudflare, Coinbase, Oracle, Fidelity?
The PayPal pattern repeats across the 2026 wave:
- Cloudflare: 1,100 jobs, single-day announcement — closer to the Meta pattern; immediate documentation push
- Coinbase: 700 jobs (14% of staff) — similar one-day pattern
- Oracle: 30,000+ across multiple tranches in 2026 — multi-month pattern, closer to PayPal
- Fidelity: 800 jobs cut while simultaneously hiring thousands — restructuring pattern; affected people may have internal transfer options worth documenting
For one-day waves, document quickly the day of. For multi-tranche reductions, document on the quarterly cadence described above. Either way, Convert: Anything to PDF is the conversion layer that lets you handle any source format without uploading sensitive material.
Convert: Anything to PDF vs the alternatives
| Tool | Local conversion | DOCX | XLSX | Images | HTML | Merge | Cost | Account |
|---|---|---|---|---|---|---|---|---|
| Convert: Anything to PDF | Yes | Yes | Yes | Yes | Yes | Yes | Free | None |
| Adobe Acrobat | Mixed (cloud or local) | Yes | Yes | Yes | Yes | Yes | $$ | Yes |
| SmallPDF | No (cloud) | Yes | Yes | Yes | Yes | Yes | Limited free | Yes |
| ILovePDF | No (cloud) | Yes | Yes | Yes | Yes | Yes | Limited free | Yes |
| Wondershare PDFelement | Yes (desktop) | Yes | Yes | Yes | Yes | Yes | $ | Yes |
| Microsoft Word | Yes | Yes (only) | No | No | No | No | If Office owned | Yes |
| Mac Preview | Yes | No | No | Yes | No | Limited | Free | No |
If you're choosing on privacy, "Local conversion: Yes" + "Account: None" is the answer. For free, in-browser, multi-format work on sensitive HR documents, Convert: Anything to PDF is the closest match.
What to do today, even if you're not affected yet
Whether or not you're in the 4,760, this week is the right time to:
- Install Convert: Anything to PDF and Convert: Web to PDF.
- Set up the five-packet folder structure on your personal machine (not your work laptop).
- Convert your current performance review, equity vest schedule, and benefits documents to PDF as a baseline.
- Update your résumé and convert to PDF.
- Capture the internal severance terms page (if visible) for your reference.
That's a one-hour setup. It puts you ahead of 90% of the population the day a notification lands.
A note on AI tools and severance review
Many 2026 startups pitch "AI severance review" or "AI negotiation help" that requires uploading your separation agreement to an LLM service. Don't, at least not with the original document.
A safer pattern: build an anonymized version of your situation ("8 years tenure, fintech engineering manager, ~$X equity vesting in next 12 months, offered N weeks severance"), feed that to whatever AI assistance you want, and never let the original document leave your machine. You get most of the value of AI assistance with none of the data exposure.
For comparing the current AI models themselves without sharing your data, CineMan AI provides a side-by-side view of the major models in one Chrome extension.
Frequently asked questions
Q: When will the first PayPal tranche land?
PayPal has signaled 2–3 years for the full 4,760 reduction but hasn't published a public tranche schedule as of May 2026. Treat each quarterly reorg as a potential trigger and document proactively.
Q: Will severance terms be the same across tranches?
Multi-year reductions sometimes see severance terms shift between tranches as company financials change. That's exactly why capturing the terms at the moment they apply to you is important — they may not be retroactive if a later tranche has different terms.
Q: How does PayPal's severance compare to Meta's?
Meta has publicly stated 16 weeks + 2/year + 18 months of healthcare for the May 20 wave. PayPal hasn't publicly disclosed its severance package, but US tech-industry standard for a multi-tranche reduction is typically 12–20 weeks base plus tenure formula.
Q: Can I save a Google Docs separation agreement as PDF?
Yes. Open the Doc in your browser and use Convert: Web to PDF — or use Google Docs' own Export feature and then archive the resulting PDF with Convert: Anything to PDF if you need to merge it with other files.
Q: Is converting in a Chrome extension really private?
Yes. The extension reads files in the Chrome extension sandbox and writes the PDF back to disk. There's no network round-trip and no third party in the loop. You can verify with Chrome's network inspector that no requests are sent during conversion.
Q: What about my internal Confluence pages — they have my work history?
Save them before access closes. Use Convert: Web to PDF on each page you want to keep. Internal Confluence pages disappear from your view immediately on separation; you cannot recover them later through any official channel.
Q: Should I save Slack DMs?
If your company allows Slack export and you have legitimate reason (your own messages, work-related), yes — but be thoughtful. Some companies treat Slack export as a TOS violation; check your employee handbook.
Q: Can I sign separation agreements via DocuSign and still have a clean PDF?
Yes — DocuSign produces a signed PDF when complete. Save it, and archive the final version through your packet structure.
Q: What if my severance is in equity acceleration rather than cash?
The Carta or Shareworks page showing the acceleration schedule is critical. Save it as PDF the day it's confirmed. Equity providers occasionally update their UIs in ways that obscure historical schedules; a PDF snapshot freezes the version you negotiated against.
Q: How long should I keep this archive?
Tax records: 7 years (IRS statute of limitations is generally 3, but 7 is the safe default for major events). Equity records: until all the equity is exercised/sold and the taxes settled. Performance records: indefinitely — they help with future references and patterns.
Q: What if I'm offered an internal transfer instead?
Same workflow, different packet. Document the original role, the offered role, the comparison terms, and any "transition incentive" specifics. If the transfer doesn't work out and you're separated later, the documentation strengthens any continuity-of-employment argument.
Q: Does Convert: Anything to PDF preserve comments and track changes in DOCX?
Visible comments and accepted track-changes appear in the PDF. For full revision history, keep the source DOCX alongside the PDF — the PDF is for archival and sharing; the DOCX is for forensic review.
Bottom line
A 4,760-person, 2-3 year layoff plan is a paperwork project that runs in slow motion. The right preparation isn't urgent on any one day; it's consistent over many months.
Convert: Anything to PDF — local, free, handles every format — is the conversion layer that makes the documentation discipline sustainable. Pair it with Convert: Web to PDF for HR portals and internal pages, and you have everything you need to stay ahead of whatever the next 2-3 years bring.
Twenty minutes a month is the price. The payoff is showing up to whatever happens, whenever it happens, with a clean and complete record.