Card designer
3 minutesto print-ready files

Mainland China uses 90×54mm (with a 90×50mm narrow option), and 85×55mm is the common Western size. Artwork needs 3mm bleed on all four sides, so a finished 90×54 card is a 96×60mm file.

Yes, and it is the whole pipeline. The panels live in a bottom drawer (Add / Layout / Content / Properties / Page), and selecting an element opens its properties automatically. The export panel is grouped by “send to print / send to someone / keep a copy”, so PDF, A4 imposition, vector SVG, card images, photoreal mockups, a QR poster, .vcf, share link and email signature are all one tap away on a phone. Pinch to zoom, drag to pan, and paste a screenshot with Ctrl/⌘+V — or drop an image straight onto the canvas — to add a photo. No account, nothing uploaded.

The print shop will convert to CMYK in the end either way. The bleed-and-crop vector PDF this site exports has two colour modes: by default it goes out in screen RGB and the shop’s RIP separates it; tick “CMYK separation” and the vector part is written directly as DeviceCMYK, neutrals go through the black plate only, total ink is held under 250%, and the canvas shows the resulting press shift live. Neither mode carries an ICC output intent, so for long runs let the shop separate against its own ICC, or proof a short gang run first.

Under “Page” in the editor there is gang-run imposition: the same card is laid out automatically on landscape A4 (6 per side for landscape, 8 for portrait), front and back each get their own sheet, neighbouring cards share one cut line, and every card keeps its own 3mm bleed. A corner copy shop or an online printer can open the sheet as is; when the count does not divide evenly, one extra sheet carries just the remainder.

PDFs exported from web tools usually have no bleed and no CMYK, and cannot convert text to outlines, so the print shop has to add all of it. The PDF exported here writes TrimBox / BleedBox / CropBox and ArtBox explicitly, includes crop marks, embeds fonts as subsets, and can optionally write the vector part directly as DeviceCMYK.

No. If you never moved an element by hand, this site re-runs the same geometry at the target size, so the result matches picking that size’s template directly. If you dragged, added, or edited something, elements are moved proportionally one by one under one rule — type sizes never change (a 9pt name stays 9pt at any size). Only positions and box widths move, text box heights are recomputed from the actual re-wrap, content is clamped back inside the 3mm safe area, and blocks that bleed off the edge are not clamped (they were meant to be cut). You are told how many were clamped and which preflight notes remain. Swapping landscape and portrait is a redesign, and it says so.

Yes — at least 15mm a side. That is a commitment to the print shop, not just a hint: if a layout places the code below the floor at a smaller size, it is automatically raised back to 15mm and pulled inside the safe area, rather than leaving a 13.9mm code waiting to be rejected. Dot-style codes or ones with a centre graphic are harder to scan, so the editor reminds you at 20mm separately.

Two floors: side ≥15mm, and each module ≥0.4mm. The second is the one people miss — when the code holds the whole card, bilingual fields can exceed 130 modules, leaving each module about 0.1mm inside a 15mm box. A phone cannot focus at card distance: it looks like a code and will not scan. This site therefore chooses the payload by box size (full card → name · phone · company → web address only) and lowers the error-correction level when needed. Quiet zones follow print practice, square modules save the most space and scan best, and dot styles are recommended at ≥20mm.

Yes, along three paths depending on what you have: read a .vcf exported from your contacts or mail client directly; paste text copied off a card (a label like “Mobile:” or “Email” in front of the value makes it most accurate); or photograph a paper card — OCR runs in the browser and the recognised text goes through the same “text → field” rules, listing what it recognised, filling only empty slots unless you explicitly choose “overwrite everything”, and the whole step is undoable. Two things to state honestly: the photo is not uploaded, it is only read once in your own browser, but the recognition models (Chinese and English packs, a few tens of MB together) are fetched from a public CDN when they are not already on the device; offline, or on iPhone where the browser blocks it, the interface says so immediately and keeps the “copy it in by hand” fallback in place. Most competitors send the photo to their server to recognise it.

No — the tag is yours. On Android, Chrome / Edge can write an ordinary NFC sticker (NTAG213 / 215 / 216) straight from the web page, and the “write to an NFC tag” button in the export panel writes this card’s vCard text. When the full card has too many fields for a small sticker it defaults to the “name / phone / company only” version and says why. Nothing passes through a server after writing. iPhone’s Safari and desktop browsers cannot open the write channel; in those cases the panel says so and puts the exact string in a copyable field so any tag-writing app can use it. Two more things stated plainly: this site’s share link carries the whole card in the URL fragment (about 4.5KB measured), so it is not suitable for NFC — that job goes to the QR on the card poster; and “change my details and everyone’s card updates” is deliberately not offered, because it would mean your card living on someone else’s server. A link you send is a snapshot of that moment.

Yes, and where it lands is computed by the layout: 13 layout geometries ship with a photo slot (Portrait photo above text, Portrait full-width back photo, Portrait photo band through the middle, Portrait photo sidebar, Portrait photo with a code, Photo left, text right, Photo across the bottom, Rounded photo, Full-bleed photo with type over it, Photo right, text left, Round headshot, Photo across the top, Full-bleed photo on the back), assembled into 51 templates. Once you pick an image it is scaled proportionally to at most 2400px in the browser, then rasterised at 300dpi with crop, corner radius and tint — so the composition you see on canvas is the one that prints in the PDF. If a face gets cropped, tap the nine-point focus to move the crop; a white-background logo or a rough cut-out can be de-backgrounded in one click (transparency is kept in the PDF via a transparency mask). Photos are never uploaded, and share links do not contain them — export PDF or image if the photo has to travel with the card.

One thing to state up front: the code on paper scans into a contact entry (vCard), not this page — their phone offers “add contact”, and name, phone, email, company and address all land in one go. We never quietly swap that for a web link. To get people onto this page, use the code on the poster below (that one carries a link) or send the link directly. What the card’s own code holds depends on the box: if it fits, the whole card; a 15mm box cannot hold that many modules (a phone cannot focus at card distance), so it automatically drops to “name · phone · company” or just the web address — the properties panel and the “handled automatically” section of preflight say exactly which, and one click grows the code so the full payload fits back in. This page itself is the card face, the name and title, plus a row of actions built from whatever you filled in: call, add on WeChat (copies the ID and gives the three paste-and-search steps), email, open in maps, open the website, save to contacts, and “book a time”: download an .ics for your calendar (defaults to the next weekday at 10am, 30 minutes, a 10-minute reminder before the call) or use the Google / Outlook web calendar deep links — all three paths use the same moment. Fields you left empty get no button, so nobody can hit a dead link. Two images can be saved from here: the 300dpi card image and a QR poster (card face + name + a scannable code, 1080×1350), enough for WeChat and for a signature block. WeChat’s built-in browser blocks external links, so when we detect WeChat the page goes straight to “open in a browser” guidance.

At the top of the layout panel on the right of the editor there is a “recently used” strip: every time you change layout, that one floats to the front marked “just now” or “3 days ago · used 4 times”, and one tap takes you back — no starring, no remembering names. It deliberately ignores the filters and search above it (people switch to the “photo” set and still want the vertical one from five minutes ago), though anything that cannot fit the current size is hidden first — a template you cannot use is worse than one you cannot see. This is separate from favourites: a star means “I decided these are good”, recent means “these are the ones I have been touching”, and mixing them turns every mis-tap into a favourite. The list lives only in this browser and is not part of the backup file — losing it when you change devices is not losing anything.

Fill the four English fields under “Content” (name in English / job title in English / company name in English / address in English), then filter by the “bilingual” facet: 6 layout geometries really have English placed (Chinese front, English back, Chinese and English on one side, Portrait bilingual, Portrait side-by-side bilingual, Portrait bilingual footer band, Portrait bilingual, both sides), assembled into 23 templates. The arrangements are Chinese front / English back (both sides share one coordinate set, so flipping gives you the same card rather than a re-set one), Chinese left / English right on one side with a divider, and portrait with Chinese on top and English below. The exported .vcf writes the English as four separate properties — FN;LANGUAGE=en, TITLE;LANGUAGE=en, ORG;LANGUAGE=en, ADR;LANGUAGE=en — so it does not collide with the Chinese line and contacts search finds you in English too. For a team batch, add “name in English / job title in English / company in English” columns to the spreadsheet; a header carrying an English marker is never mistaken for a Chinese field. Every English field is optional — leave them empty and it is an ordinary Chinese card. If you pick a bilingual layout and the back really is empty, preflight says “this side is a blank side” instead of letting you print it.

Use the batch page: paste a CSV / TSV exported from Excel (or pick a local file). a header that says Name, or the Chinese for name or given-name, all resolve to the name column, and a wrong guess is one manual fix. Everyone gets the same frame and the same type sizes, each card’s QR is generated from that person’s own details, and what you export is already mixed A4 imposition — however many front sheets, however many back sheets, 6 per sheet (8 for portrait), with a footer naming the sheet number and card count. Up to 100 people per run, entirely in the browser; the roster is never uploaded.

Yes. Save the background, text colour, brand colour and logo once in the brand kit (up to 12 kits, kept only in your browser), and every geometry across 215 layouts is redrawn by role colour, so applying it makes them your colours — the same kit applies to a whole employee roster at once. On save, this site runs a WCAG contrast check: text against background must reach 4.5:1, brand colour and small text 3:1; if something fails it names which item, and one click fixes it by adjusting lightness only (hue is preserved, so your primary VI colour is not replaced).

The icons are not a font — they are vector shapes from Fluent UI System Icons (MIT licensed, commercial use allowed), converted to Bézier curves on export, so the PDF and SVG hold real curves that neither shift nor drop glyphs on another machine.

Every font on this site is SIL OFL or explicitly free for commercial use (Source Han Sans, Source Han Serif), usable on the web and embeddable in the PDF. Uploading your own font asks you to confirm you hold a commercial licence for it.

No. A third-party page analytics tool is loaded on the site. It records clicks and scrolls, to show which step people get stuck on. Nothing on the card — name, phone, email, company, address, photo — is within what it records. Designing, previewing and exporting all happen on your own device, and there is no server copy. If you would rather not be recorded, block it in your browser; no feature is lost.

Designing, previewing, print-grade PDF (subset font embedding), vector SVG and the .vcf contact card are all free and need no account. Anything charged later would be long-term hosting and team features — never the download button.