Most free video makers online either stamp a watermark on your export, force you to sign up, or upload your photos to a server you know nothing about. If you just want to turn a batch of pictures into a video with music for Reels, Shorts, or a family memory reel, none of that should be necessary.
Here's how to make a photo slideshow video with your own music, right in your browser, with no watermark and nothing uploaded.
Where your video will be watched determines the shape it should be. Getting this right before you export saves you from re-doing the whole slideshow later.
Best for YouTube and TV playback.
Perfect for Reels, Shorts and Status.
Fits neatly into a square feed post.
No upload, no watermark, no signup. Your photos and music never leave your device.
Make My Slideshow →A slideshow feels far more finished with a soundtrack. Add your own MP3, M4A or WAV file and the tool automatically fits the track to your slideshow's total length, with optional fade in and fade out so the music doesn't cut off abruptly.
For Reels, Shorts or Status, switch to the 9:16 vertical layout so your photos fill the screen without black bars. Keep each photo on screen for two to three seconds if you have a lot of images, or longer if you're building a slower, more cinematic memory reel.
Not necessarily, but if your photos are very large files from a modern phone camera, running them through the Image Compressor first can make the slideshow build faster, especially on older devices.
A photo slideshow rendered as video is a sequence of still frames written at a fixed frame rate, with an audio track laid alongside. At 30 frames per second, a photo held for four seconds occupies 120 identical frames. Video codecs handle that efficiently — repeated frames compress extremely well — which is why slideshow videos are usually far smaller than their duration suggests.
It also explains why motion effects change everything. A slow zoom across a still image means every frame differs slightly, so nothing can be reused and the file grows substantially. Whether that trade is worth it depends on the platform: a subtle drift holds attention on social feeds, while a static hold is perfectly fine for a family album.
| Purpose | Seconds per photo | Notes |
|---|---|---|
| Social reel or short | 1.5–2.5 | Fast cuts hold attention in a feed |
| Event recap | 3–4 | Long enough to recognise faces |
| Wedding or memorial | 4–6 | Viewers want to linger |
| Product or portfolio | 2–3 | Enough to read a caption |
Simple arithmetic keeps expectations honest: 60 photos at four seconds each is four minutes. If your music track is three minutes, either trim to 45 photos or shorten the hold to three seconds. Deciding this before you start saves rebuilding.
Choose the ratio before assembling, because changing it later means re-cropping everything. Vertical 9:16 fills the screen on phone-first platforms. Square 1:1 is a safe compromise for feeds. Horizontal 16:9 is right for YouTube, television and anything watched on a laptop. Mixing portrait and landscape photos in one video always leaves letterboxing somewhere; deciding in advance whether to accept bars or crop is easier than fighting it afterwards.
Using a commercial song in a video you publish is a licensing question, not a technical one. Platforms run automated identification, and the usual outcomes are muting, blocking in some countries, or the rights holder claiming any revenue. For a private family video this rarely matters. For anything public, use music you have actually licensed, tracks from a library that grants the rights you need, or genuinely royalty-free material — and keep a record of where it came from.
Practically, fade the audio in over the first second and out over the last two. An abrupt start and a hard cut at the end are the clearest signals of a video assembled in a hurry.
Frames are composited in your browser and encoded through its own recording pipeline, so the container and codec are whatever your browser provides rather than a format you select. That is fine for sharing, uploading and family archives. If you need a specific codec, a precise bitrate or frame-accurate control, re-encode the result in a desktop tool. Very large photo sets at high resolution can also exhaust a tab's memory, so build long slideshows in sections and join them afterwards.
Images and audio are read from disk and composited locally. Nothing is uploaded, there is no account, and no copy remains anywhere after you close the tab. Family photographs are among the most personal files most people own, and handing a folder of them to a free online service means handing over a complete copy. You can verify this one: watch the Network tab in developer tools while building, or disconnect from the internet after the page loads and carry on.
About 1.5 to 2.5 seconds for social clips, 3 to 4 for an event recap, and 4 to 6 for a wedding or memorial where viewers want to linger. Multiply by your photo count first - 60 photos at four seconds is a four-minute video.
Most popular music runs between 90 and 130 beats per minute. At 120 BPM one bar is two seconds, so holding each photo for two, four or six seconds puts your transitions on the beat. It reads as noticeably more polished.
Decide before you start, because changing it later means re-cropping everything. Use 9:16 for phone-first platforms, 1:1 for feeds and 16:9 for YouTube or anything watched on a laptop or television.
Technically yes, legally it depends. Platforms run automated identification and commercial tracks are commonly muted, blocked in some regions, or monetised by the rights holder. For anything public, use properly licensed or genuinely royalty-free music and keep a record of the source.
Filenames sort alphabetically rather than numerically, so photo 10 lands directly after photo 1. Rename with zero-padded numbers - 01, 02, 03 - and the sequence will hold.
Rotation is stored as an EXIF flag rather than in the pixels, and not every pipeline honours it. Open the photo in a viewer, rotate it and save, which rewrites the actual pixels and always carries through.
No. Images and audio are read from your device and composited entirely in your browser, with nothing transmitted or stored. Check the Network tab in developer tools while building, or disconnect from the internet after the page loads.