Chrome 151 Drops macOS Monterey: Your PDF Workflow Needs a Plan

TL;DR

Chrome 151, released July 28, 2026, requires macOS 13 Ventura. Chrome 150 was the last version supporting macOS 12 Monterey. If your Mac can't run Ventura, you are now on a Chrome build that will never receive another security patch.

That's not a "your browser looks old" problem. Chrome has had five zero-days disclosed and patched this year. Every future one stays open on your machine indefinitely. The browser stops being a reasonably-hardened piece of software and becomes the softest thing on your computer.

Which changes the calculus on how you handle documents. The reflex answer to "I need to convert this file" — open a website, upload the file, download the PDF — was always a privacy trade. On an unpatched browser it becomes a security one too, because you're logging into third-party services and handing them files through a rendering engine nobody is fixing anymore.

The better shape for an old Mac: do the conversion locally, in as few moving parts as possible, with as few sites in the loop as possible. Convert: Anything to PDF converts images, text files, markup, and CSV entirely inside the browser — no upload, no account, no server round-trip. Fewer parties touching your files means fewer places an unpatched browser can hurt you.

This post covers what actually changed, how to check where you stand, what your realistic options are, and how to structure a document workflow that doesn't depend on a browser you can no longer patch.

What changed, precisely

Google raised Chrome's minimum supported macOS version with Chrome 151. The specifics:

• Chrome 150 — last release supporting macOS 12 Monterey.
• Chrome 151 — stable July 28, 2026; requires macOS 13 Ventura or later.

If you're on Monterey, Chrome won't uninstall itself or stop launching. It will simply stop updating. You'll keep running 150 forever, with a version-number badge that quietly stops moving.

This is normal, scheduled behaviour — Google has raised the macOS floor several times, and Apple stopped shipping security updates for Monterey some time ago. The mechanics aren't surprising. What's worth thinking about is the consequence, which most coverage skips.

Which Macs are affected

macOS 13 Ventura dropped support for a batch of hardware, roughly: MacBook Pro models from 2016 and earlier, MacBook Air 2017 and earlier, iMac 2016 and earlier, Mac mini 2014, and the 2013 Mac Pro. If you're on one of those, Ventura was never available to you and this is where the road ends for Chrome.

Check your position in two clicks:

• macOS version: Apple menu → About This Mac.
• Chrome version: chrome://settings/help — it'll show your version and tell you whether updates are still flowing.

If that page says you're up to date on 150.x while the rest of the world is on 151, you're in the frozen group.

Why an unpatched browser changes how you should handle files

Let's be specific rather than alarmist.

A browser is the most-attacked piece of software on a normal person's machine. It executes untrusted code from every site you visit, by design. The reason that's tolerable is that the code runs inside a sandbox that gets hardened continuously, and when someone finds a way out, it's patched within days.

Remove the patching and the model changes. The sandbox is still there — it's not as if the browser becomes wide open. But every newly discovered escape stays usable against you for as long as you keep using that build. And browser zero-days get reverse-engineered from the patch itself, so exploit availability follows disclosure by a short interval. We covered the pattern when Chrome's fifth zero-day of 2026 landed.

Now apply that to document workflows. The typical online-converter flow involves:

1. Visiting a third-party site you may not have vetted.
2. Loading its ad and analytics stack, which is often the actual risk surface.
3. Uploading a file — possibly a sensitive one.
4. Trusting its retention policy.
5. Downloading and opening the result.

Each step is a place where an unpatched renderer matters more than it used to. Step 2 in particular: ad networks are a well-worn delivery path for browser exploits, and free conversion sites are heavily monetized by exactly that.

Meanwhile the local-extension flow is:

1. Open a file you already have.
2. Convert it in-process.
3. Save it.

No third-party site. No upload. No ad stack. The attack surface isn't zero — nothing is — but it's a fraction of the alternative, and on a frozen browser that fraction is worth a lot.

Your realistic options, ranked

Option 1: Upgrade macOS if you can

Obvious, and worth checking before anything else. If your Mac supports Ventura or later and you've been putting the update off, do that and stop reading. You get Chrome updates back and Apple's security patches with them.

Option 2: Switch to a browser that still supports your macOS

Firefox has historically maintained support for older macOS versions longer than Chrome, and Firefox ESR longer still. This is a genuine option and for many people the right one.

The trade-off, stated honestly: our extensions don't run on Firefox. Convert: Web to PDF, Convert: Anything to PDF, and ScrapeMaster all depend on Chromium-specific APIs — the DevTools Protocol print path and the Side Panel API — that Firefox doesn't implement. We're not going to pretend otherwise to keep you on Chrome. A patched Firefox with different tools beats an unpatched Chrome with ours.

Check the current Firefox macOS support matrix before committing; these floors move.

Option 3: Stay on Chrome 150 and shrink your exposure

If upgrading isn't possible and switching browsers isn't practical, this is where most people land. It's defensible if you're deliberate about it:

• Reduce the number of sites in your workflows. Every site you don't need to visit is a risk you don't take.
• Do file operations locally. Conversion, merging, and export should happen on your machine, not on someone's server.
• Keep your extension count low and audited. Check host permissions at chrome://extensions and set anything you can to "On click" rather than "On all sites."
• Use a separate, patched machine for high-value logins — banking, work systems, anything with real consequences — if you have access to one.
• Treat the old Mac as a content-consumption and local-work machine, not a general-purpose everything machine.

That's not a perfect posture. It's a reasonable one, and it's a lot better than continuing as though nothing changed.

Option 4: Move the workflow off the browser entirely

macOS has built-in tools that don't involve Chrome at all, and on a frozen browser they deserve more use than they usually get:

• Preview merges PDFs, reorders pages, and exports images to PDF.
• Print → Save as PDF works from any app.
• Quick Actions in Finder can create PDFs from selected images.

These handle a real slice of the work. What they don't handle well is anything web-shaped — a rendered page, a CSV that needs table formatting, a Markdown file, a JSON structure — which is where an extension still earns its place.

What Convert: Anything to PDF actually does locally

Since the argument here is "fewer parties, less network," it's worth being exact about the tool rather than hand-waving.

Supported conversions, all in-browser:

It also merges multiple files into a single PDF, which is the operation most likely to send someone to an upload site.

And the honest limits, because a tool's boundaries matter more than its feature list:

• No OCR. A scanned image becomes an image in a PDF. The text inside it is not searchable, because nothing is reading it.
• No native Word or Excel parsing. Excel goes through a CSV export first — that's the documented workflow, not a hidden limitation. .docx isn't a supported input.
• No cloud anything. No account, no sync, no storage. If you close the tab, nothing persists anywhere.
• Chromium only. Chrome, Edge, Brave, Arc, Opera, Vivaldi. Not Firefox, not Safari.

That last one is exactly the tension in Option 2 above, and it's why we're laying it out plainly rather than burying it.

A workflow that survives a frozen browser

Concretely, for someone on an unpatchable Mac who still has documents to handle:

For files already on disk — receipts, screenshots, exported CSVs, Markdown notes — convert locally with the extension or with Preview. Zero sites involved.

For web pages — order confirmations, dashboards, articles, portal pages — use Convert: Web to PDF on the page you're already logged into. This is strictly better than pasting a URL into an online converter, which can't reach a logged-in page anyway and would need you to visit another site to fail at it.

For merging — do it in the extension or in Preview. Not on a website.

For anything genuinely requiring software you don't have — a real .docx conversion, OCR on a scan — use a different machine if you can, or accept the risk consciously rather than by default. Knowing which category a task falls into is most of the benefit.

The broader point about tool longevity

There's a lesson here beyond macOS versions.

Workflows that depend on a live service have an expiry date set by someone else. The service shuts down, changes pricing, gets acquired, or drops support for your platform, and your process breaks on their schedule. We watched this play out when Apryse acquired PDF Tools and Smallpdf, and again with OpenAI's Atlas shutdown.

Workflows that run locally on files you already have degrade far more gracefully. A local converter on a frozen browser still converts. A cloud converter can revoke your access tomorrow, and an unpatched browser makes reaching it riskier besides.

That's not an argument that local is always better. It's an argument that when your platform is aging out, local is what keeps working.

Frequently asked questions

What macOS version does Chrome 151 require?

macOS 13 Ventura or later. Chrome 150 was the final release supporting macOS 12 Monterey. Chrome 151 reached stable on July 28, 2026.

Will Chrome stop working on my Monterey Mac?

No. It keeps launching and browsing. It stops receiving updates, which means it stops receiving security patches — so every zero-day disclosed from now on remains unpatched on that machine.

How do I check whether my Chrome is still updating?

Go to chrome://settings/help. It shows your version and whether updates are still available. If you're pinned at 150.x while current stable is 151 or higher, you're on the frozen branch.

Is it dangerous to use an unpatched browser for online PDF converters?

It raises the risk meaningfully. Online converters mean visiting third-party sites, loading their ad and analytics stacks, and uploading files — and ad networks are a well-established delivery path for browser exploits. On a browser that will never be patched again, minimizing the number of untrusted sites in your workflow is the single most useful change you can make.

Should I switch to Firefox instead?

If your Mac can't run Ventura, that's a reasonable choice — Firefox has generally supported older macOS releases longer, and Firefox ESR longer still. The trade-off is that our extensions don't work on Firefox; they rely on Chromium-only APIs. A patched Firefox with different tools is a better security position than an unpatched Chrome with ours.

Can Convert: Anything to PDF handle Word documents?

No. .docx isn't a supported input. Supported formats are JPEG, PNG, WebP, SVG, GIF, BMP, TXT, HTML, Markdown, JSON, XML, CSV, and the active web page. Excel data goes through a CSV export first.

Does the extension have OCR for scanned documents?

No. A scanned page converts into a PDF containing that image, and the text in it stays unsearchable. The extension preserves text that already exists as text; it doesn't create a text layer where there isn't one.

Does converting a file send it anywhere?

No. Conversion runs entirely in your browser. There's no upload, no server round-trip, and no account. That property is the whole reason it's a sensible choice on a browser you can no longer patch.

Bottom line

Chrome 151 requiring Ventura turns a lot of still-perfectly-usable Macs into machines running a permanently unpatched browser. The hardware is fine. The browser is the problem, and it's a problem that only grows.

Upgrade macOS if you can. Switch browsers if you can't and our extensions aren't load-bearing for you. If you're staying on Chrome 150, be deliberate: fewer sites, fewer uploads, local file operations, tight extension permissions.

Convert: Anything to PDF converts images, text, markup, and CSV to PDF entirely on your machine, with no account and no upload. On a browser nobody's patching anymore, keeping your files off the network is the cheapest security win available.

CineMan AI is in the same category of "does its job without phoning home" — IMDb and Rotten Tomatoes ratings on Netflix, Prime Video, and Disney+, free, no account.