SiteSucker Pro 6.2.2 for macOS

Version 6.2.2 of SiteSucker Pro requires macOS 26, and the build runs natively on both Intel and Apple Silicon machines. That’s the hard requirement—no workarounds for older operating systems.

Once you’re on a compatible Mac, the app automates pulling down a site’s pages, images, and files so you can browse everything offline. The Pro edition adds a practical twist: it can grab embedded YouTube and Vimeo videos that a standard downloader would skip. If you only want certain file types, the File Types section lets you limit the haul to images or PDFs instead of grabbing everything. By default, it respects robots.txt exclusions, so you won’t accidentally vacuum up sections the site owner asked crawlers to leave alone.

The toolbar gives you an Open Log button that tracks every operation from the moment downloading starts, and you can send that log straight to Console when you need to dig into what happened. Settings are split into straightforward sections—General, Logs, Limits, File Types, Paths, and Advanced—so you can dial in exactly how aggressive or polite the crawler should be.

Crawler blocked mid-grab

A site grabs fine over a browser but comes out broken in SiteSucker Pro, and you're staring at a folder of files that don't quite work. Nine times out of ten the problem is the crawler getting blocked by a cookie wall or a JavaScript redirect. The fix is usually in the Advanced settings—switch the user-agent from the default to Safari or Firefox, and the remote server suddenly treats the download like a real visitor instead of a bot. That alone clears up more headaches than any other single setting.

Another common snag: you point sitesucker at a domain and it pulls in half the internet, running for three hours before you finally stop it. That's the Limits section doing nothing when you needed it to. Before you hit a big site, set a link depth of two or three levels and cap the total file count. You can always come back and widen the net later, but walking back an overstuffed download folder is a chore nobody needs.

If PDFs or videos aren't landing, check that you haven't accidentally filtered them out in File Types. The Pro edition handles embedded YouTube and Vimeo content, but only when the file-type filter isn't set to block everything except HTML and images. And when the log shows a string of "skipped" entries with no obvious reason, the robots.txt exclusion is usually the quiet culprit—toggle it off in settings if you're sure you should be crawling those paths.

Start with a small, single-section site

Don't point sitesucker pro at a sprawling news site right out of the gate. Pick something small—a documentation site, a personal blog, a single-section reference—and watch how the local folder mirrors the original structure. Open a few pages locally and get a feel for what broke and what survived. That ten-minute test teaches you more about the Paths and Limits settings than reading the preferences window ever will.

Make a habit of naming your download folders with the date and the site, not just the domain. Six months from now you won't remember whether "docs_project" was the January snapshot or the March one. A folder called docs_project_2025-01 saves you from guessing.

If you're archiving something for reference, grab the log file through the toolbar button right after the download finishes and stash it next to the site folder. When a page doesn't open properly down the road, that log will tell you whether the file was never downloaded in the first place or something else went wrong on your end.

• macOS 26 or later
• Intel or Apple Silicon Mac