A lit cake takes about a minute: open a cake picture or a looping candle video, go full screen, raise the brightness and drop the room lights. No web page will react to your breath — reaching the microphone needs a permission prompt cake pages never ask for — so have someone cut the screen on the cue.
A browser is genuinely good at part of this. It is already on the laptop, the tablet and the television, it needs nothing installed, and a big screen in a dim room is a better centrepiece than a phone in someone's hand. When the requirement is a cake on a screen in the next sixty seconds, the browser wins outright and nothing else comes close.
What the browser is not allowed to do is listen to you uninvited. Microphone access on the web only works in a secure context, meaning an HTTPS page, and the browser has to ask the visitor for permission before any audio input is opened. A page that was never built to ask can never react, no matter how convincing the flame looks. That single rule is why nearly every birthday cake page online is an animation or a video rather than something you blow out.
Sound has its own rule, and it surprises people at the worst possible moment. Browsers allow muted playback to start on its own, but audio waits for a signal that a human is present: a click or tap on the site, a history of playing sound there, or the site being installed. So the tab you opened, muted, and pushed to full screen ten seconds before the singing may well sit in complete silence when you need it.
Open a cake picture or a looping candle video and go full screen, F11 on Windows or Control-Command-F on a Mac, so no address bar, tabs or bookmarks are in the shot. Push screen brightness to maximum and turn the room lights down. A flame on a screen only reads as a flame when it is the brightest object present; in a lit room it reads as a photo of a flame, and the difference is immediately obvious to everyone watching.
Click once on the page and let a second of sound play, then mute it and wait. Browsers hold back audio until you have interacted with the site, so a page you opened silently and never touched will stay silent exactly when the singing starts. Doing this early, while people are still arriving, costs nothing and removes the single most common failure of the whole plan.
Set the display to sleep after ten minutes or never, and turn on do-not-disturb so a message banner does not slide across the cake. On a laptop, plug the charger in: battery saver dims the screen on a schedule of its own, and that schedule has no idea the singing is about to start. Check the screen is still awake right before you gather people, not after.
Put two slides in whatever presentation tool you already have: slide one is the cake with candles lit, slide two is the same picture darkened, with grey smudges rising off the wicks. Run the slideshow full screen and press the arrow key on the cue. A key press is far easier to time than closing a tab, and it does not dump everybody back onto a desktop covered in file icons and notifications at the emotional high point of the evening.
Count three, two, one out loud while raising fingers. Everyone blows on one, and whoever is on the keyboard presses on one. The visible count matters more than the spoken one as soon as a camera or a call is involved, because sound reaches different people at different moments while a raised hand reaches everyone at once.
Share the specific tab rather than the entire screen, so incoming messages and notifications do not land on top of the cake. In the sharing dialog, find the option for sharing tab or system audio and make sure it is ticked: without it your side sings and their side watches a silent flame. Test it with one person a few minutes before, because the sharing dialog is not where you want to be experimenting while fifteen people wait.
This page was written by DKsequence. We also make the Android app recommended below — the steps above work whether or not you install it.
A website could technically do it, since browsers do expose microphone input, but only over HTTPS and only after asking you for permission, and the page has to be built to ask. Most birthday cake pages online are animations or videos that never request the microphone, which is why they do not respond to anything you do at them.
Because browsers allow muted playback to start on its own but hold back audio until you interact with the site. Click anywhere on the page once and the sound will start. Do that a few minutes early rather than at the moment everyone starts singing.
Yes, and it is the best version of the browser route. One bright screen in a dark room is what makes candles on a screen convincing. Cast the tab or plug in an HDMI cable, go full screen so no browser furniture is visible, and if it is going out on a call, remember the share-audio option.
Share the tab rather than the whole screen, tick the option to share its audio, and count down out loud while raising fingers. Audio arrives at slightly different times for different participants, so a visible count keeps everybody together in a way a spoken one does not. Take the lit photo before the countdown, not after.
Browser, no question: a cake picture on a full-screen laptop with the lights down takes a minute and needs nothing installed. Reach for an app version instead when you want the birthday person to blow the candles out themselves, or when you will be doing this again next month and do not want to rebuild the slides every time.