2026-09-02

DIY wedding graphics from your own photos — where the transparent cutout fits, and where it stops

The Knot's running list of the most popular wedding dates of 2026 has five entries — June 6, June 20, September 19, September 26, and October 10 — and three of them land in the six weeks after this post goes up. That's the shape of the modern wedding calendar, not a fluke: the press release for The Knot's 2025 Real Weddings Study (built on nearly 17,000 US couples who married in 2024) names fall the top wedding season and October the single most popular month, at 17%, and the same study line reports over 67% of 2023's couples married in summer or fall. Money frames the season just as tightly. The Knot puts the 2024 national average cost at $33,000; Zola's 2026 First Look Report — its largest survey ever, over 11,500 engaged couples — has the average holding at $36,000 for a second year, and reports that 60% of couples call managing their actual budget against online inspiration their number-one pain point, up 12% in a year, with nearly half adjusting their budget because of what they saw online. Squeezed between a saved-inspiration folder and a five-figure invoice, plenty of couples end up building some of the graphics themselves — the welcome sign, the save-the-dates, the wedding website, the seating chart. This post is about the one small, unglamorous step most of those projects share: getting the two of you out of a photo and onto a transparent background. And about exactly where NearBG's part of that job starts and stops.

Where a couple photo actually shows up

Trace a guest's path through a fall wedding and count the designed surfaces carrying the couple's picture: the save-the-date that arrived months earlier, the wedding website where they RSVP'd, the welcome sign at the entrance, sometimes a seating chart or a photo timeline of the couple growing up, occasionally a cardboard standee of the couple (or of the dog who wasn't allowed to attend — this blog's standee post covers the print mechanics of that one), and the thank-you card that shows up afterward. Every one of these is a layout job done in a template tool or handed to a print shop, and in every one the design supplies its own background — the painted acrylic, the cream cardstock, the website's hero section. Which means the photo can't arrive as a photo. It has to arrive as the subject only: the two of you, alone, on transparency, so the sign's design can run behind you instead of whatever parking lot or pier the engagement shoot happened in front of.

The rectangle is the tell

Paste an ordinary JPEG into a designed sign and you get the photo plus its own background, in a hard-edged box. However lovely the original shot, the sign now has a rectangle of somebody's backyard floating in the middle of its typography — the visual equivalent of a sticker that didn't get cut out. A transparent-PNG cutout is the difference between "a photo placed on the sign" and "the couple standing in the sign's design." That's the entire reason this step exists, and it's worth seeing side by side:

Same sign, same photo. The only difference is whether the photo arrived with its own background still attached.

The cutout pass, and why on-device quietly fits this job

NearBG's role in all of this is one narrow pass per photo: drop the picture in, the model separates the subject from the background entirely inside your browser tab — nothing is uploaded, no account, no server ever holds a copy — then a touch-up brush with a size slider erases anything the automatic pass wrongly kept (the sliver of pier between your elbows, the stranger's shoulder at the frame's edge), and a reset button reverts to the untouched automatic result if a stroke goes wrong. The download is a PNG at the original photo's full resolution, which matters more here than in most projects: a welcome sign prints big, and a cutout downsized on the way out would show it. The on-device part isn't a slogan in this context either — engagement photos are exactly the pictures most people would rather not hand to an anonymous server, and wedding DIY means running dozens of very personal photos through tools in a short window.

One non-technical note that belongs in any honest version of this post: engagement photos are usually a professional's work. Removing a background doesn't change who owns the image — check your photographer's contract or print release before putting a shot on anything printed large or sold, the same as you would for any other use of their photo.

The honest hard cases: veils, loose hair, and bouquets

This blog's hair post explains why segmentation models struggle with fine detail — every pixel gets a hard in-or-out decision, while wisps of hair are genuinely a blend of subject and background — and wedding photos happen to concentrate the worst inputs for that limit in one place. A veil is the extreme case: semi-transparent fabric is nothing but blended pixels, so expect the model to keep it as a solid shape or drop parts of it, not to preserve its see-through quality — that would take matting, which NearBG doesn't do. Loose updo strands behave like the fur this blog's pet post describes. Bouquets add their own trap: airy filler like baby's breath is full of tiny gaps the mask will bridge or swallow. The practical moves are the same as ever — pick a sharp, well-lit photo with decent contrast between you and the background, expect cleanup at the edges, and remember the brush only erases: a dropped veil edge can't be painted back in, because the brush removes pixels rather than restoring detail the mask never caught.

What NearBG deliberately doesn't do here

One photo per pass, no batch mode. The couple photo for the welcome sign, the childhood photos for a timeline display, each set of parents for the seating chart — every one is its own run.
No resizing or cropping to a print spec. Whatever pixel dimensions your print shop or template wants, that adjustment happens in the design tool, not here — NearBG hands you the cutout at the original photo's resolution and stops.
No sign templates, fonts, mockups, or backgrounds. The eucalyptus border, the script typeface, the painted-acrylic look are all the design tool's job. NearBG never composites your cutout onto anything; it only removes.
Keep the download a PNG. Re-saving as JPEG silently fills the transparency back in as a white box — the exact failure this blog's print-on-demand post documents from the printing side — and a welcome sign is an expensive place to discover it.
Start the printed pieces early. Signs and seating charts have print lead times, and the cutout is the first file in that chain — a fall date means the crunch is now, not the week of.

The honest summary

Every outside number above has a named source: 2026's five most popular wedding dates (June 6, June 20, September 19, September 26, October 10) and the 67%-in-summer-or-fall figure come from The Knot's own dates article drawing on its Real Weddings Study of 10,474 couples married in 2025; "fall is the top season, October the most popular month at 17%" and the $33,000 2024 average come from The Knot Worldwide's press release for the 2025 Real Weddings Study; the $36,000 average and the 60%-budget-pain-point figure come from Zola's own press release for its 2026 First Look Report, a survey of over 11,500 engaged couples. The claims about the tool come from the tool's code: an on-device pass that turns one photo into one transparent PNG at original resolution, an erase-only brush with a reset, honest roughness where veils and loose hair meet a segmentation model's hard edges — and a boundary that ends exactly where the sign templates, print specs, and seating-chart layouts begin.