Use Case
3D UX/UI mockups that scroll inside a laptop and a phone
Full page screenshots scroll inside a 3D laptop, app screens tap on a 3D phone, hotspots link out. One URL that opens in any browser, nothing to install.
3 min
Deliver a wedding album flipbook: sixty edited photos, real page turns, one link a grandparent can open on a phone with nothing to install.
The photographer delivers a gallery of eight hundred images. The couple opens it once, saves a handful of frames, and never goes back. What they wanted to send their families was an album of sixty. A gallery and an album are different products, and shipping only the first is why most wedding photography gets looked at once.
A gallery exists so nobody misses the photo of their aunt. An album exists to tell the story of the day in a sequence somebody chose. Deliver both and label them clearly. The album is forty to eighty images in a chosen order, made to be opened rather than downloaded. In i3Dify the wedding album is an album project: the photos go in, the pages auto-paginate at four per page, and that setting takes one, two, three, four or six depending on how much room a spread needs.
The viewer already knows what happens. Prep, ceremony, portraits, reception, party. Sequencing against that order asks people to reassemble the day in their head, and they will not do it. Inside the sequence, alternate wide and close: one establishing frame, then two or three intimate ones, so a spread reads as a scene instead of a contact sheet. Give the ceremony and the first dance a spread each at one photo per page, and end on the last photo of the night rather than a portrait. Photos reorder by dragging them in the list, so the order is one pass of the mouse, not a re-upload.
The album opens as a hardcover, and the cover is the only page some people see before deciding whether to keep going. You pick the cover color or gradient, type the title, which is almost always the two names and the date, and choose the font. Use the invitation font if the couple had one. Individual photos can carry a hotspot, so a guest nobody recognises in fifteen years still has a name attached to the frame. That is the difference between a link that looks like a delivery and one that looks like a book.
The people most likely to want the album are the least likely to survive a gallery login, a download and a photo app. The album is a URL. It opens in the browser, pages turn from the arrows in the dock or the arrow keys, and there is nothing to install and no account to make. Check the type size on the cover: a name set small on a laptop is a name nobody can read on a phone held at arm's length. Then send the link to the couple and ask them to forward it to their parents themselves. Forwarded by the couple it gets opened. Sent by the photographer it reads as marketing.
Visibility is Private, Unlisted or Public, and most wedding albums want Unlisted: not listed, not indexed, open to whoever holds the link. On top of that you can require a password to open the page, which the couple hands out to family. The limit is worth saying plainly: the password covers the page, not the direct image URLs, so treat it as a lock on the door rather than a safe. Downloading is off until you turn it on, so the album stays a viewing object and the gallery does file delivery. Sharing and distribution also covers the QR code PNG and the embed code.
Free gives you three projects and 50 MB of storage, and every free project carries the i3Dify watermark. There is no way to turn that off on free. For a sixty-image album you either resize the exports, which is what a screen-first deliverable wants anyway, or move to Pro at 3 dollars a month for 10 GB, unlimited projects and no branding. A studio delivering one album a week hits the three-project ceiling in the first month.
Sixty photos in the right order, at a link that opens on any phone, is the version of the day the couple actually forwards. The gallery is the archive. The album is the thing people look at. Start from the 3D wedding album template.
A gallery is complete and downloadable so nobody misses a photo. An album is forty to eighty edited images in a chosen sequence, made to be opened and forwarded. Deliver both, clearly labelled, because they serve different people at different moments.
Forty to eighty. Enough to tell the story of the day, few enough that every image earns its place. The album auto-paginates at four photos per page, and you can drop the strongest twenty to one per page. The other seven hundred live in the gallery.
Almost always. The day has a narrative the viewer already knows, so prep to ceremony to portraits to reception reads as a story. Alternate wide establishing shots with close intimate ones, and end on the last photo of the night.
Not by default. Downloading is off until you turn it on, so the album stays a viewing object. Enable it on the gallery instead, which is where file delivery belongs.
No. Print is the heirloom. The link covers the six weeks after the wedding when everyone wants to see the photos and the printed album does not exist yet, and it makes the printed one easier to sell.
The couple sends it to dozens of people who are themselves getting married. Put the studio name on the final page, keep the URL permanent, and send the link back to the couple on their first anniversary.
Full page screenshots scroll inside a 3D laptop, app screens tap on a 3D phone, hotspots link out. One URL that opens in any browser, nothing to install.
Pixieset delivers a gallery couples download once. A 3D wedding album is a hardcover with their names on the cover, at one link, from 0 to 3 dollars a month.
Transform your content into immersive 3D experiences in seconds.
Create Flipbook