Can't save pages in Safari--only active is Escape...

Hey there, Nestor,

Thanks for visiting the Apple Support Communities. It sounds like you are having difficulty saving Safari pages on your Mac. You've come to the right place to get some help!

To get started, we recommend using the steps in the Apple Support article If Safari on Mac doesn't open a webpage or isn’t working as expected - Apple Support.

If you still are having trouble after that, see if you can reproduce it in safe mode: Start up your Mac in safe mode - Apple Support.

Best!

Thanks for getting back in touch, Nestor.

Since the issue continued in safe mode, the next recommendation would be to try duplicating it in a new user account: Set up users, guests, and groups on Mac - Apple Support. If it works there, it will let us know something specific to your user account is causing it to occur.

Should it not work in a new user, however, you'll need to get in touch with Apple Support directly for additional assistance. You can do that here: Get Support.

Have a wonderful day!

Good idea Nestor, didn't think about that.

I really hope they take a look at this, it's so annoying to me because I use webarchives a lot.

I even tried rolling back to Safari 14 which of course they make impossible. I'd have to re-install the OS, too much pain.

I already filed a bug report, maybe if you have the patience you can do the same.

It's done here:

https://www.apple.com/feedback/safari.html

Funny. :-( Ok, maybe we must search for our own.

I just have a look in the logs:

standard 20:40:10.994560+0100 SafariBookmarksSyncAgent Process com.apple.SafariBookmarksSyncAgent did release lock: com.apple.WebBookmarks.SafariTabs.lock

standard 20:40:12.267779+0100 com.apple.Safari.SandboxBroker CoreAnimation: failed to receive fence reply: 10004003

standard 20:40:12.292196+0100 com.apple.Safari.SandboxBroker <NSViewServiceMarshal: 0x7ff7dfc186c0 <NSRendezvousSheetController: 0x600003cecaa0 <NSSavePanel: 0x7ff7dfd13b10>>> encountered accessory view with unexpected class NSView

fehler 20:40:12.701569+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.701608+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.701632+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.701651+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.701668+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.720892+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.720937+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.720962+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.721860+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.721900+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.721925+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.723000+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.723040+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

fehler 20:40:12.723063+0100 com.apple.Safari.SandboxBroker mach error 0x10000003: (ipc/send) invalid destination port

standard 20:40:19.502502+0100 Safari 0x118ae87e0 - [PID=0] WebProcessCache::setApplicationIsActive: (isActive=0)

standard 20:40:19.609603+0100 SafariBookmarksSyncAgent Process com.apple.SafariBookmarksSyncAgent did acquire lock: com.apple.WebBookmarks.SafariTabs.lock

standard 20:40:19.611943+0100 SafariBookmarksSyncAgent Process com.apple.SafariBookmarksSyncAgent did release lock: com.apple.WebBookmarks.SafariTabs.lock

I see this messages when i try to save a page.

Tomorrow i will learn, what "invalid destination port" means ...

Too bad the Apple screwed up saving web pages when they revised Safari to version 15. And too bad that the "experts" at Apple are so busy with marveling at the latest versions of Mac OS that they couldn't help you (or me) with our "old" Catalina.

After clicking Save As, you can use the keyboard Cmd-S to save the Web page---but it saves only as an html file, not as a webarchive. The advantage is that it can be opened in any browser; the disadvantage is that it may not look the same when reopened.

I learned about this "trick" after intensive fruitless searching, and finally noticing at https://iphoneteile.com/530149/making-webarchives-on-Safari-15-2-on-Catalina-10-15-7/ the remark that "I can manipulate the save page with the keyboard" and remark by Missing Fe that "The created file (webarchive) also effected, it’s no longer a “webarchive” file which is unique to safari, now it’s a “html” file instead. If we reopen the file, it’s not a complete page that we save earlier."

There is something else going on. Very few users have complained. My wife and I both have Mac OS 15.7 and Safari 15; but on her machine Safari still works as it used to, saving webarchives. I can't detect what is different.

Perhaps there is some other "hidden" key combination that will allow saving as a webarchive (hint: It isn't Cmd-W). Maybe the Apple "experts," if they bother to explore instead of giving pat answers, or if maybe they would consult the engineers who mangled Safari, they might even be able to discover it and let the rest of us know.

Hello Nestor, the same thing is happening to me on my iMac and MacBook Pro, both with Catalina and Safari fully patched.

One thing I notice is after pressing CMD+S to save a page, a window pops up on the bottom left of my screen for a very brief split second before disappearing, after which the normal Safari Save dialog comes up. Can you check if this also happens to you? It might be a clue...

I have exactly the same issue, which suddenly started out of the blue maybe a few weeks ago. I *think* it was after I (foolishly) relented to some endlessly annoying prompt by Apple about "updates are available"—which usually I never do.

I'm on a 2019 iMac, Catalina 10.15.7, Safari 15.2 (with a string of numbers after it in parentheses, whatever those are).

I've tried everything I know, and finally have had to chew leather and use another browser. Has anybody found any new clues to solving this mess?

I'm having the SAME ISSUE!

I CANNOT SAVE a page as a web archive.

When I go to File>Save As, the save and cancel buttons do not work. If you press enter (to save), it saves it as an html file instead and press esc (to cancel)

Maybe it's because of Safari Version 15.3 (15612.4.9.1.8, 15612).

Apple, FIX THIS NOW !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Yes, I can reproduce that exactly. Saving a PDF incl. selecting destination folder works.

Maybe worth noting that this leads to a (partial) workaround for selecting a destination folder for saving html only (no webarchive): Go to a page with a PDF, cmd-s, select the desired destination folder, press the cancel button, go to the html page you want to save, cmd-s, now the previously selected folder should still be selected, cmd-s again should now store the plain html here.

@Apple: Please fix. I would prefer to stay with Safari as default browser, but if elementary bugs are not fixed...

My OS: 10.15.7 (19H1715)

Safari: 15.3 (15612.4.9.1.8, 15612)

Thanks for these suggestions. Nonetheless Apple MUST fix the bugs.

In my case, sometimes an extra effect of the bug is that after asking "save as", (1) the dialog box for choosing the destination file remains open despite hitting ESCAPE and (2) the Mac becomes progressively less responsive to the keyboard. Aftera a while no other program responds to the keyboard. (3) The solution is "force-quit" Safari using the mouse alone, or press the power button to force shutdown before the Mac crashes all by himself.

Can Apple please pay attention and as a minimum let customers know what Apple knows about the bug?