For years now the number of tabs consistently open in Chrome on my iPhone has been, well, an unknown but certainly large number. Since long ago the number of open tabs on my phone has been at least 100. I know this because the tab "button" at the bottom of the mobile Chrome screen carries on it a two digit indicator, displaying how many tabs you have open, since that isn't apparent given the single-tab-focus interface afforded us by the phone's display. I know this because once you have more than 99 tabs open, Chrome for mobile completely stops keeping track for you how many tabs you have open, replacing the digital indicator with a sideways smiley emoticon, which I will admit does feel like an appropriate symbol as the number of open tabs on a handheld device approaches ludicrous levels. The ASCII emoji seems sorta like an Easter egg from the Chrome mobile engineering team, as a way to say "lolwtf?" in response to my habit of keeping an ungodly quantity of tabs open, waiting to be read.
Now, of course, anyone who has used Chrome on a PC knows that trying to sustain normal machine functions while running Chrome with 100 tabs open is a foolish endeavor, and that eventually your machine will grind to a halt because of it, or you will assist its inevitable suicide once Chrome has started to get all... Chrome-y. You’ll definiteley have to force-kill the app at some point, regardless of the quantity of open tabs or allegedly free system resources. Hopefully you have hit shift-ctrl-d before it gets to that point, bookmarking all the urls in tabs intended for another day that just hasn't come. But I digress. (I do that a lot in the course of writing up this "quick" how-to, and if you're already feeling a bit TL;DR, you may click that to scroll to the actual instructions, skipping my lead-up commentary.)
It's actually been a source of some consternation that at any point in time I expected Chrome for iOS to go the same route as Chrome for Windows has; that is, devolve into crappy software that is extremely frustrating to use, and that some day, like has happened many times on Windows machines, Chrome will crash and die, and the sessions open at that time will be lost, unrecoverable... where even tedious manual searching through history cannot be entirely succesful even if one were willing to spend that much time and effort trying. On my iPhone though, Chrome is rock solid. The way that it deals with (or doesn't) open-but-not-in-focus tabs is efficient and reliable, and Google needs to consider applying the same sort of solution to the its non-mobile namesake so that using the product is not the cycle of bloat/crash/kill, which inevitably becomes part of a desktop Chrome user’s normal workflow.
Anyway, where I was going with this and am slowly getting around to actually stating, is that the results from Googling how to bookmark all tabs on mobile Chrome would lead one to believe that there is no equivalent in the mobile app to shift-control-d on PC, and also no shortage of people offering convoluted solutions to the problem in public forums, such as using the Chrome Sync functionality to view the mobile device's open tabs from your pc’s Chrome history, and then select and open them all(since there is no way to do what would seem obvious - right-click on a url in history and "add bookmark") in Chrome on your pc and then bookmark them there, which can be synced back to your mobile device. While that would work, it would be in no way convenient, epecially when dealing with the unkown - but doubtlessly very large - number of tabs that I would be dealing with.
Even if that approach was the only way... As has been discussed up to now, opening 100+ tabs on the Windows version of Chrome is not a given to win. Attempting that will kill even my 16 core 5GHz i9 with 32GB RAM sure as shit so I don't really see it as a viable option, though you saw me.. I tried. And the other obvious solution to having thia vast quantity of tabs I'm not looking at (but don't want to *lose*) doesn't sound any more attractive really, which would be just individually bookmarking and closing them one at a time. It might take as long as it has for me to accumulate them in the first place as well.
So today (well, not really today, but rather the day I started writing this document that I just found on *actual* today today, unfinished but evidently published to a live site in an incomplete and embarrassing state. Though the article is titled as an instructional to finally provide a correct answer to the how to question, I had put this document online without actually explaining how-to. I just sorta lamented the state of Chrome for PC and then pasted a GPT-3 summarization of what I had written so far at the bottom. *shrug*) - today I am here now to remedy that. I figured out how to bookmark all in mobile Chrome, and in doing so doscovered what the smiley face tab count indicator represents in my case, and figured some may find it interesting. (The magnitude of the number surprised even me.)
Now that I'm writing this (again), it occurs to me that perhaps I could have stayed better on task if I had taken a more positive approach to writing initially on the topic, perhaps focusing on how remarkably well Chrome on iOS works - both in general, and especially as compared to Chrome on a desktop platform. But, that said... who among us has not become disillusioned with Chrome today and nostalgic for the performance it once offered tnd delivered to us that prompted us to switch to it in the first place so many years ago, when it was Mozilla increasingly suffering from bloat. And then.. there was ie. Internet Explorer was, well.. still ie, and not much more needs to be said about that. Chrome had been the shot in the arm that web browsing needed at the time, but now, today... the once spritely and powerfuli browser leads the others only in terms of frustrating bloat, insufferable lag, and oh, so much crashing. Mozilla has urely seen Chrome's sorry state and perhaps sees in it another chance at winning the browser wars with Firefox, and heck.. even Microsoft is in the game now for that matter, since Bing now has CHatGPT - if you use Edge (and have been accepted to early access), making even the modern evolution of ie (which is itself based on Chromium) begin to look enticing. So I take little personal responsibility for the tone of this message
I should take a moment, however, to give thanks and props to the team responsible for the Chrome on iOS product. It knows how not to waste resources on tabs that aren't presently in focus, which I suspect accounts for the majority of the difference between the two solutions. I've probably said enough on the matter though already, and you probably came here to learn how to save all open tabs as bookmarks in Chrome on iOS but have been subject to my random stream-of-consciousness bashing of Chrome for desltop to this point.
I will delay no further... I've even now taken some screenshots from my phone so that when I link to this updated version of the doc, hopefully it will be decent to look at and easy to read. (I write this page ssh'd into my webserver, editing in vim, manually adding html markup as I go along. I'm not really a front-end guy, as is most certainly obvious. I should probably consider making use of a blogging platform or some such, but old habits die hard I guess.)
The image with the marked up arrow shows the area where, for up to 99 tabs, Chrome had displayed a count of how many I had open. You can see the old school ASCII sideways smiley face where the number used to be. It has been this way for years as I continue to accumulate open tabs, with apparently no negative impact on iOS Chrome's performance.
That many. That's how many browser tabs I have open on my phone presently. I've been asked, and now I can answer.
Oh yes, that was my intent when I started writing this, wasn't it? That's what lead you here yet I've spent all of this time complaining, while yet resisting the urge to rail against unbounded leaky memory hogging Chrome essentially DoS'ing my system if I dare to leave it running even while I am using some other app. I haven't even mentioned the out-of-control google crash handler processes that serve some ironic purpose other than recovering from unexpected faults and I have already exceeded any estimable word count for writing on this topic by a good measure, all without really discussing the main topic inteded for this article! So perhaps I can deliver to you now the elusive instructions for the equivalent of shift-control-d on Windows within the mobile app, by way of pictures which surely are worth thousands of these words.