How to Export a NetrunnerDB Decklist for Printing Without Missing Cards

TLDR

For reliable NetrunnerDB export decklist printing, decide the deck’s format first, validate the saved deck, separate the identity and other outside-the-deck cards, and keep optional testing cards out of the production count. Export or copy the list using the controls currently available on NetrunnerDB, then compare the source deck, review list, and printer confirmation line by line. Do not approve printing merely because the final total looks plausible.

The export itself is the easy part. The expensive mistakes happen when an old deck version, an optional card, a missing identity, or an incorrect quantity survives into the final order. A good NetrunnerDB export decklist printing workflow therefore treats the decklist as data that must pass several checks—not as a block of text that can be copied and forgotten.

Start with the intended format or card pool

Before checking individual cards, write down where the deck is meant to be played. A deck for Standard, Startup, Eternal, Core Sets, a locally defined card pool, or unrestricted casual play may require different cards and legality checks. Null Signal Games maintains the official Supported Formats page for current card pools and restrictions. Check it close to the date of printing because format pools and balance restrictions can change. If the deck is intended for an event, also confirm the format with its organizer rather than inferring it from the deck’s age or title.

This decision belongs at the beginning because printing the wrong format is not a production defect. Every card can be rendered and cut correctly while the resulting deck is still unusable for its intended event. If you are choosing between the two more common starting points, the Standard versus Startup comparison explains how card-pool size changes what you may need to print.

For casual play, define the agreement just as clearly. Record whether the group allows every card, follows a historical pool, uses current card text, or has house restrictions. “Casual” removes the need to satisfy an official tournament format; it does not remove the need for both players to understand the card pool.

Check the legal deck before creating the print list

Open the exact saved version of the deck you intend to print. Check its side, identity, main-deck count, copy limits, influence, and—if it is a Corp deck—agenda points. NetrunnerDB decklist data distinguishes the identity from card slots and records quantities, total card count, and influence spent, making those fields useful checkpoints rather than decorative summary numbers.

Confirm that the list has one correct Runner or Corp identity and that every main-deck card belongs on the same side.
Verify that the main deck meets the identity’s minimum deck size. More than the minimum may be legal, but it changes consistency and can change Corp agenda requirements.
Review every quantity. Under the general rule, a deck may contain no more than three copies of a card by name unless the card itself provides a different limit.
Check influence card by card. Each copy of an out-of-faction card contributes its influence cost, so a correct card name with the wrong quantity can make the deck illegal.
For a Corp deck, verify the agenda-point total against the final deck size. The comprehensive rules specify 18–19 agenda points for 40–44 cards, 20–21 for 45–49 cards, and 22–23 for 50–54 cards, with a formula for larger decks.
Apply any additional restriction imposed by the selected format. Do not assume that ordinary deck-construction checks cover every current balance or format rule.

These checks establish legality, but they also protect printing accuracy. Influence and agenda totals are useful error detectors. If an exported quantity changes, those totals may change even when the overall number of lines looks normal. For a fuller deckbuilding walkthrough, see how to build and print a legal deck with NetrunnerDB.

Separate the identity, required extras, and optional cards

A Netrunner print package can contain more than the main deck, but those components should not be merged into one undifferentiated count. The comprehensive rules distinguish the deck from the identity, player aids, and cards that begin the game outside the deck.

Use four visible sections during review: identity, main deck, required outside-the-deck cards, and optional flex cards. The identity must be present for play, but it is not part of the main-deck count. If a card or identity requires another card to begin outside the deck, list that component separately and verify the relevant card text or rule.

Treat maybeboard entries, matchup experiments, and replacement options as a flex stack. Normal Netrunner play does not use a conventional sideboard, so optional alternatives should not silently enter the production quantity for the active deck. Netrunner Android’s broader decklist-to-print workflow likewise recommends checking identities, side separation, quantities, and special extra components before production.

You may still print flex cards. Just give them their own labeled section and total. That preserves the choice to revise the deck later without creating ambiguity about which cards belong in the playable list now.

Build a printing-friendly review list

Create a plain-text review copy before submitting anything. This is a human-readable proofing template, not a claim about the syntax accepted by a particular importer:

FORMAT: Standard, Startup, Eternal, Core Sets, event-specific, or casual pool
SIDE: Runner or Corp
IDENTITY: 1 — Full official identity name
MAIN DECK: quantity followed by the full official card name on each line
MAIN-DECK TOTAL: final number of cards, excluding the identity and outside-the-deck components
CORP AGENDA TOTAL: final agenda points, if applicable
INFLUENCE: final influence used and the identity’s limit
REQUIRED EXTRAS: cards or components that begin outside the deck
OPTIONAL FLEX CARDS — EXCLUDED FROM MAIN DECK: quantity and official name for each testing option

Keep commentary outside the production section. Notes such as “try two copies,” “alternate art preferred,” or “replace after rotation” are useful to a player but can be misread as card lines by an automated parser or by a person preparing files. Preserve official card names and explicit numeric quantities.

A clean structure also helps if you switch production methods. Whether you print at home, use Netrunner Android’s current decklist workflow, or submit files through a general printing platform, the same proofed source list gives you a stable reference. Input methods vary, so follow the live service instructions rather than assuming that a NetrunnerDB URL, pasted list, or particular file type will be accepted.

Export or copy from NetrunnerDB carefully

Use whichever export or copy option is currently presented for the saved deck on NetrunnerDB. Interface labels and available formats can change, so the important requirement is the output: it should preserve the exact official card names and quantities from the intended deck version.

Open the saved deck version you actually intend to print, not an older revision or a published inspiration list.
Record the deck title and revision date in your private notes so you can identify the source later.
Export or copy the main deck without editing quantities during transfer.
Copy the identity into its own labeled field if the export does not include it clearly.
Move any maybeboard or optional entries into the separate flex section.
Add required outside-the-deck cards under their own heading.
Save an untouched copy of the export before adapting it to a printer’s required input method.

Netrunner Android states that its printing workflow allows users to import a decklist and confirm quantities and print selections. The exact live input control should determine whether you provide pasted text, a supported file, or another form of input; do not convert the list based on an assumed format.

Perform a three-way final proof

The strongest final check compares three representations of the same deck: the NetrunnerDB source, your plain-text review list, and the printer or file-generation confirmation. Compare them line by line. A matching grand total is not enough because one missing card and one accidental duplicate can cancel each other out.

Check	Source versus review list	Review list versus print confirmation
Identity	Same full name and side	Included once and not counted as a main-deck card
Main-deck cards	Every name and quantity match	Every selected card and quantity match
Deck total	Matches the saved legal list	Matches the confirmed production count
Agenda points	Correct for the Corp deck size	Agenda cards and quantities remain unchanged
Influence	Matches the validated deck	No substitutions or quantity changes
Required extras	Listed separately	Included only in the intended quantity
Flex cards	Clearly excluded from the main deck	Printed only if deliberately selected

If the production system displays images, inspect them as well as names. Stop if a card appears to use an unexpected printing, language, face, or version and the service does not make the intended choice clear. Resolve ambiguity before approval rather than assuming that a familiar title guarantees the expected output.

For home production, proof one page before committing to the full deck. Scaling and cropping are separate from decklist accuracy; the Netrunner card scaling guide covers that stage. If you outsource production, take a screenshot or save the final confirmation so you can compare it with the source list.

Check proxy requirements for event play

A correctly exported and printed deck is not automatically acceptable at every event. Null Signal’s organized-play policies permit proxies when the applicable requirements are met, including requirements related to sleeve fit, physical consistency, required card information, and avoiding extra information. Review the current organized-play policy hub and follow any additional organizer instructions before the event.

Opaque sleeves and physically consistent cards protect hidden information. From a gameplay perspective, the question is not merely whether a card can be recognized when accessed; it is also whether its location can be inferred from a different back, thickness, edge, or feel. When uncertain, ask the organizer before printing or sleeving the deck.

Final NetrunnerDB export decklist printing checklist

The intended format or casual card pool is written down.
The latest applicable card pool, balance restrictions, and event instructions have been checked.
The saved NetrunnerDB version is the version intended for printing.
The deck has one correct identity on the correct side.
The main deck meets its minimum size.
Every card respects its copy limit.
Influence is within the identity’s limit.
A Corp deck has the correct agenda-point total for its final size.
Any additional format-specific deckbuilding restriction has been checked.
The identity is separated from the main-deck count.
Required outside-the-deck cards are listed separately.
Maybeboard and testing cards are labeled as optional flex cards.
Every official card name and quantity survived the export.
The source, review list, and final production confirmation match line by line.
Event proxy requirements and organizer instructions have been checked where relevant.

Common questions

Does NetrunnerDB export directly to a printer?

Do not assume a direct connection. Use NetrunnerDB’s currently available export or copy controls, then follow the printer’s live submission instructions. The proofing workflow remains the same whether the service accepts text, a file, or another input method.

Does the identity count toward deck size?

No. The identity is necessary for the deck but is distinct from the main deck and does not count toward its card total.

Does Netrunner use a sideboard?

Normal play does not use a conventional sideboard. Keep optional replacements and testing cards in a separately labeled flex stack so they cannot be mistaken for part of the active deck.

Can I print four copies of a card?

You may choose to print spare copies for a collection or multiple decks, but a single deck generally cannot contain more than three copies by name unless the card specifies another limit. Separate collection quantities from the legal quantity in the active deck.

What is the best final step?

Read the final production confirmation against the source deck one line at a time. Verify names, not just totals; isolate extras; and approve the job only when all three versions agree. That short proof is what turns an export into a dependable playable deck.