{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Proof{{ resultsReady ? `${computation.values.readiness_percent}%` : '—' }} Format{{ formatMeta.label }} RSVP{{ rsvpModeLabel }}
Use an ampersand, plus sign, or the word “and” between names.
Updates the card, message, email, and wording ledger.
Choose 5 × 7 for a classic print invitation or 9 × 16 for phone stories.
The production proof flags incompatible format and medium choices.
Controls the RSVP line and QR payload.
Leave blank when the couple is hosting without a separate host line.
Keep timing or transport details on the wedding website when possible.
Use a familiar phrase such as cocktail, garden formal, or black tie optional.
Keep the front-card note to one concise sentence.
This setting changes the production proof, not the screen palette.
Use a six-digit hex color such as #8b5e3c.
Uses initials derived from the couple names.
{{ include_monogram ? 'Enabled' : 'Disabled' }}
Scan the QR from the final exported artwork before sharing.
{{ include_qr ? 'Enabled' : 'Disabled' }}
{{ previewExportStatus }}

The chart renderer is unavailable. The same fit values remain in the production proof.

{{ chartExportStatus }}
ArtifactCopy-ready textCopy
{{ row.label }}{{ row.text }}
{{ tableExportStatus }}
Proof itemStatusNext actionCopy
{{ row.label }}{{ row.ok ? 'Ready' : 'Review' }}{{ row.action }}
{{ tableExportStatus }}
Quick Response (QR) Code Generator Create a QR code for links and common actions with payload-capacity and contrast checks plus quiet-zone, logo, and scan-readiness guidance.
QR Label Sheet Generator Create printable QR label sheets from CSV or text rows with stock presets and placement planning plus density warnings and local processing.
Bingo Card Generator Create reproducible bingo card packs from your own prompts, with seeded shuffling, duplicate cleanup, coverage checks, and caller order.
Image Cropper Crop one image locally with exact aspect and pixel controls, then review upscaling and transparency along with quality or file-budget risks.

Guests should not have to piece together a wedding invitation from several clues. The names, event, date, local time, venue, and reply method need to read as one clear message. Tone and decoration can make the card personal, but missing or crowded details create practical problems such as late arrivals, replies sent to the wrong person, or a phone image that crops the address.

Printed cards and digital invitations put different pressure on the same wording. A 5 × 7 inch portrait card gives familiar space for a ceremony invitation, while a 9 × 16 story format favors short lines that remain legible on a phone. A square or landscape card changes line length again. Choosing the medium early prevents a design that looks balanced in one proportion but cramped in the final one.

Invitation wording
The host line, couple names, and sentence that identify who is inviting the guest and what they are invited to attend.
Event facts
The date, local start time, venue name, and address a guest needs to arrive at the right place.
RSVP handoff
A website, email address, or phone number paired with a reply deadline when responses are required.
Supporting details
A short reception, attire, or access note that belongs on the card; longer travel and registry information usually belongs elsewhere.

Formality comes from more than a typeface. Family-hosted wording, a warm shared invitation, a destination note, and a reception-only announcement set different expectations. The wording should match the event that will actually happen. A ceremony invitation should not imply that every recipient is also invited to a separate reception unless that is true.

A QR code can shorten the path to an RSVP page, but it cannot replace readable text. Some guests will use a printed address or type a link manually, and a QR image may fail after resizing, compression, or printing on reflective stock. The final proof should therefore keep the reply destination visible and test the code from the same exported artwork guests will receive.

A production check is still a planning aid, not a printer’s proof or a guest-list system. Confirm names, event facts, privacy-sensitive contact details, paper size, bleed, safe margins, and color expectations with the people and vendor responsible for the final invitation.

How to Use This Tool:

Set the delivery format before polishing the wording, then use the proof to resolve missing details and copy-fit warnings.

  1. Choose Wording style, Design preset, Card format, and Delivery target. Pair the story format with phone-story delivery; use a print proportion for printed or mixed delivery.
  2. Enter the couple names, ceremony date and time, venue name, and address exactly as guests should read them. Correct any invalid date, time, or missing required detail before judging the preview.
  3. Select an RSVP method and provide the matching website, email address, or phone number. Add a valid Reply by date, or choose No RSVP line when replies are handled separately.
  4. Use Advanced only for details that change the finished card, such as a host line, reception note, dress code, paper or digital medium, accent color, monogram, and RSVP QR code.
  5. Review Copy fit and Production proof. Shorten any section above 100%, fix a delivery mismatch, and scan the QR code from the final PNG or PDF before sharing it.

Interpreting Results:

The readiness percentage summarizes nine checks. A 100% result means the required event details passed validation, the RSVP destination and deadline are usable for the chosen mode, the format matches the delivery target, and every measured text section is within its copy budget. It does not verify that the event facts are true or that a printer will reproduce the design as expected.

  • Copy fit at or below 100% is within the built-in planning allowance. A value above 100% identifies the section to shorten; it is not a physical type-size measurement.
  • Production proof should have no unresolved RSVP, deadline, delivery, or fit warning before export.
  • A checksum-verified guest link shows that its embedded invitation details were not changed accidentally. It does not prove who created or sent the link.

Technical Details:

The production proof combines required-field validation, mode-specific RSVP rules, format compatibility, and character-based copy allowances. These checks are deterministic, so the same invitation details produce the same readiness result.

Formula Core

Each copy-fit value compares the trimmed character count for one section with its planning limit, then rounds to the nearest whole percent.

U=round(CL×100)

Here, C is the trimmed character count and L is the section limit. The limits are 58 characters for names, 70 for the venue name, 150 for the details note, and 125 for the visible RSVP destination. These are editorial fit budgets rather than measurements of glyph width.

Readiness is the rounded share of nine successful checks, and the warning count is the number that did not pass.

R=round(P9×100) W=9−P

P is the number of passed checks, R is readiness percent, and W is the warning count. Five checks are satisfied once the required details pass input validation; the remaining four cover RSVP destination, reply deadline, delivery compatibility, and copy fit.

Rule Core

Check Pass rule
Required details Names, a real calendar date, a 24-hour time from 00:00 to 23:59, venue name, venue address, and a six-digit hexadecimal accent color must be valid.
RSVP destination Website mode needs a valid HTTP or HTTPS address, email mode needs an address-shaped value, phone mode needs at least seven digits, and no-RSVP mode needs no destination.
Reply deadline A valid date is required for website, email, and phone RSVP modes. No-RSVP mode passes without one.
Delivery match Phone-story delivery requires 9 × 16. A printed suite rejects 9 × 16 and digital-only medium. Print-and-digital delivery also rejects 9 × 16.
Copy fit The largest of the four utilization percentages must be less than or equal to 100%.

A guest link contains the invitation settings as encoded text plus a SHA-256 checksum. Loading the link recomputes that checksum and falls back to default details when the values do not match. Because no secret key is involved, someone can change the details and create a new matching checksum; the link provides neither confidentiality nor sender authentication.

Privacy and Limitations:

Invitation previews and exports are produced in the browser, but a guest link places the entered invitation details in the link itself. Treat anyone who receives that link as able to read and forward the names, venue, address, RSVP contact, and optional notes it contains.

  • Do not put private guest-list notes, access codes, meal choices, or other confidential planning data on the card or in a guest link.
  • The copy budgets count characters, not actual font metrics, printer bleed, trim tolerance, envelope size, postage, or paper behavior.
  • Date fields are checked as calendar dates, but the reply deadline is not compared with the ceremony date and no timezone is attached to the ceremony time.
  • Always proof names, dates, local time, venue directions, RSVP contact, QR scanning, and final print dimensions independently.