If your invitation guest list fails to upload, stop before importing the same file again. Check whether the platform rejected the whole file or accepted some guests, then compare its current template with your spreadsheet. Correct the specific problem, reconcile any records already added, and review the completed guest list before sending a single invitation.
First identify what actually failed
A spreadsheet can look tidy and still produce an incomplete invitation list. A column may belong to a different import template, one household member may have invalid contact information, or the upload may have reached a review screen without being completed. The right fix depends on the stage where the problem appeared.
This guide focuses on getting an initial guest-list upload into the correct event and recovering from a rejected or partial import. It is not a general address-collection worksheet or a comparison of RSVP subscriptions. If you are moving completed RSVP information between tools, use our separate guest-list export and portability guide.
Keep invitations unsent while you investigate. Record the event name, file name, time of the attempt, visible error, and number of recipients shown before and after it. Those details help you distinguish an upload problem from an accidental send or a later delivery failure.
Use the template for this exact destination
There is no universal invitation spreadsheet. Even within one service, an account address book and a particular event may use different import formats. Download the current template from the screen where you intend to add guests rather than reusing a spreadsheet that worked for another occasion.
The following differences were checked in the providers' public instructions on October 24, 2026. Treat them as examples of why a platform-specific check matters, not a promise that every account or future interface behaves identically.
| Provider | Documented import distinction | Your practical check |
|---|---|---|
| Paperless Post | Its event guest-list guide supports CSV or XLSX uploads on a computer and distinguishes the event template from the Address Book template. | Confirm that the file belongs to the event-import workflow, not merely to your saved contacts. |
| Greenvelope | Its spreadsheet workflow includes column matching and a review of upload notifications before completion. | Read the matching and notification screens before accepting the pending upload. |
| Evite | Its Excel upload instructions call for name, email, and phone columns in that order, without headers or extra filled columns. | Do not assume that a header row required elsewhere is appropriate here. |
See the official instructions for Paperless Post spreadsheet uploads, Greenvelope Excel imports, and Evite guest-list uploads before preparing your file.
Keep your master list and upload copy separate
Your working wedding or party spreadsheet may contain family notes, invitation decisions, seating ideas, and contact details. The upload copy should contain only the fields supported and needed for this event. A failed import is not a reason to hand over every column in your planning workbook.
Save an unchanged source copy, then create a clearly named upload version. For example, “Reception-guests-upload-2026-10-24-v1” identifies the event, purpose, date, and revision. Keep a short note of which rows you intentionally excluded. Otherwise, a later helper may mistake a deliberate omission for an upload failure and invite someone you were not ready to contact.
Remove template examples before using real information. Check that you exported the intended sheet rather than a notes tab or an earlier event. If a supported field is blank, leave it blank in the way the template requires; do not fill it with a guess just to make the spreadsheet appear complete.
Read the result before deciding to retry
| What you observe | What to establish | Safer next action |
|---|---|---|
| No guest records appeared | Was the file rejected, or is there an unfinished review step? | Read the message and complete or correct that stage before starting a second upload. |
| Some guests appeared | Which source rows succeeded, and which failed? | Reconcile the list and repair only the missing or incorrect entries through a supported method. |
| Count looks too high | Are these extra recipient records, intended group members, or duplicates? | Inspect identities and group structure before deleting anything. |
| Names appear under the wrong fields | Did columns map incorrectly or follow the wrong template? | Pause sending and correct the destination structure rather than merely changing the file's name. |
Do not equate a completed progress indicator with a correct guest list. A successful transfer can still contain an incorrect name, the wrong household arrangement, or an unintended contact method. Conversely, one warning does not establish that every row failed.
A partial family import needs a family-level check
Paperless Post explicitly warns that some members of a group can upload successfully while others fail. Its guidance directs hosts to inspect the group and add the failed members there. This is a concrete reason to avoid immediately uploading the entire original file again.
Consider a fictional household: Riley, Taylor, and Casey Morgan were meant to appear together. After the upload, Riley and Casey are visible but Taylor is missing. First open that group and compare the three intended people with the two existing records. Correct Taylor's source information, then use the provider's documented way to add the missing member to that group.
The mistake to avoid is creating a second “Morgan family” entry simply because the first group is incomplete. After the repair, review both membership and the invitation allowance. A familiar family name alone does not prove the group is correct. Keep an unresolved household out of a send batch until you understand what its invitation will allow.
Do not merge guests just because they share contact details
Two rows with the same email address may be an accidental duplicate, or they may represent two intentionally named people who share an inbox. A repeated surname may belong to different households. Decide what the records mean before using any automatic cleanup option.
For example, one parent may manage replies for several named family members. Your event tool's grouping method must express that arrangement; copying the same email into several independent records is not automatically the right substitute. Review the provider's household controls and your intended recipient structure together.
For another fictional case, an aunt appears once as “Alex Rivera” and once as “Alexandra Rivera.” Compare the source notes and intended invitation, then confirm whether these are the same person. Do not erase one just because the names look related. The goal is one correct invitation arrangement, not the smallest possible spreadsheet.
Try a small permitted draft check before the full list
If the platform permits a draft or test list, use a few representative records before uploading the entire event. Include an individual, a named group, and a name containing punctuation or an accent. Use only contact methods you control for any actual test delivery; invented email addresses can belong to real people.
Check the imported display and the saved records, not just the spreadsheet preview. If a character is rejected or changed, consult the provider's requirements rather than silently changing someone's name. Evite's cited instructions impose character restrictions, so verify the supported way to represent the affected guest before sending.
Also establish how the test records will be handled afterward. Do not assume that importing a production file replaces earlier entries or updates matching contacts. Confirm the service's behavior and remove only records you can identify as your own test data, using its normal controls.
Ask support a question that can be answered
If the result remains unclear, a precise report is more useful than “my spreadsheet is broken.” Explain the import destination, file type, expected entries, visible results, and exact error. Start with a redacted example rather than sending your entire guest list in an ordinary message.
For example: “I used the event guest-list template. The upload reported one failed member of a three-person group, and two members are now visible. Should I edit the existing group to add the missing person, or is there a specific retry option?” Include no real guest information unless the provider needs it and you are comfortable sharing it through its official support process.
Once the imported list is correct, review the intended recipients and group allowances again before sending. If a message later bounces, that is a separate delivery problem; our bounced invitation email guide starts from the saved recipient record rather than recommending another full-list import.
Keep physical invitation planning on its own track
A digital guest-management tool can accompany physical invitations, but an imported row is not an order quantity. Count the physical invitations you need separately from people, email recipients, and named group members.
For a physical design example, this LunaInvites clear acrylic invitation with a white monogram envelope features printed floral corners. Its digital proof is the design-approval stage of a physical order, not a guest-list import service or a downloadable invitation file.
The current shipping policy provides free US shipping and estimated total delivery of approximately 7–8 days after final design proof approval, including 2 days of production. This is an estimate, not a guaranteed arrival date. Guest-list setup, addressing, and sending invitations to guests require their own planning time.
Cover presentation: AI-assisted editorial composition based on a real LunaInvites product photograph. The checklist is illustrative; it is not a screenshot of a guest-management service.