Wedding Card

A quiet wedding card, set in a serif, ready to print.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

What a wedding card has to carry

A wedding card is an instruction sheet with good manners. It needs who, when, where, and what the guest is expected to do about it. Everything else is decoration, and decoration that pushes the time or the venue into small print is decoration working against the card.

Design for the worst reading conditions: a phone photo forwarded in a family group, printed small, or seen by someone who does not know the family names. Test those three and the card is finished.

Print a proof before the run. Card stock changes how ink sits, and a cream paper can turn a warm gold into brown. One proof costs less than reprinting a hundred, and it is also the moment you notice that the venue name is spelled two different ways.

Keep a plain-text version for the family group. Cards get forwarded as images that are hard to read on a phone, and a message with the same details is what people actually use on the day.

One card per household is the convention most families still expect.

    Good to know

    Names are set in the font you choose and printed as text, so accents and long names do not get clipped. Check the proof before ordering a hundred.

      How Wedding Card works

      Typeset a wedding card with the names, date, time and venue at print resolution. The method behind Wedding Card is the single-purpose logic inside wave40.js, and this page shows the result with its assumptions in the open.

      • Open Wedding Card and provide wedding card — the page accepts it in the field it shows.
      • For Wedding Card, canvas and CSS do the rendering; colours are converted mathematically between models.
      • The Wedding Card output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

      A worked example for Wedding Card

      A typical run of Wedding Card starts with wedding card and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

      Export once and open the file at 100%: colours and dimensions are what you set, and any surprise is the font substitution the limits section warns about. That check applies directly to Wedding Card with wedding card.

        When to use Wedding Card — and when not to

        Reasonable uses: Brand colours and palettes; Social graphics at the right dimensions; Print-ready cards and posters. Wedding Card is deliberately narrow: it does one job and states its assumptions instead of hiding them.

        Canva-class tools do more layout, but they also want an account and a canvas that belongs to them. For one card, one palette or one banner, this is faster. The honest ceiling for Wedding Card: for Wedding Card, fonts come from your device, so exact rendering varies.

        • Best case for Wedding Card: Brand colours and palettes
        • Also fine with Wedding Card: Social graphics at the right dimensions
        • Not what Wedding Card is for: for Wedding Card, fonts come from your device, so exact rendering varies.

        Reading the Wedding Card result

        The output of Wedding Card is a function of the inputs alone — no hidden state and no server.

          Accuracy and limits of Wedding Card

          The method is the single-purpose logic inside wave40.js. Wedding Card prints results at the precision its inputs justify, and the limits below are the honest ones:

          • Wedding Card: For Wedding Card, fonts come from your device, so exact rendering varies.
          • For Wedding Card, exports are raster (PNG/JPEG/PDF) unless SVG is offered.

          Privacy and speed on the Wedding Card page

          The Wedding Card page is a static file plus wave40.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

          Speed follows the build: Wedding Card loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

            What you get from Wedding Card

            The output of Wedding Card appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the design work finishes the moment the numbers are in.

            Because Wedding Card is built from wave40.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

              Questions

              What if the names are long?

              The title scales down automatically until it fits the width.

              Is it editable after download?

              No — regenerate from the fields and download again.

              How accurate is Wedding Card?

              The method is the single-purpose logic inside wave40.js. For Wedding Card, fonts come from your device, so exact rendering varies.

              What are the limits of Wedding Card?

              For Wedding Card, exports are raster (PNG/JPEG/PDF) unless SVG is offered.

              Is anything uploaded when I use Wedding Card?

              No. Wedding Card runs entirely in the browser tab; nothing is uploaded, stored or logged.

              Can I use Wedding Card offline?

              Yes — Wedding Card keeps working offline once the page has loaded; the whole tool is a local script.

              Keep going

              More design tools