TLDR: Netrunner shared card pool storage works best when you organize by use before organizing by card name. Keep complete decks intact, give teaching decks their own zone, sort the active building pool for fast retrieval, and move rotated or historical cards into a clearly labeled archive. Track both the source of the card image and the type of physical print so nobody mistakes a print-and-play card for a finished product.
A shared collection fails when every card is technically present but nobody knows whether it is available. The real goal is not perfect filing. It is letting several players build, borrow, return, and update decks without competing for invisible copies or mixing formats. If you are still deciding what the collection should contain, start with building a shared community library card pool, then use the system below to keep it usable.
Build five storage zones before sorting individual cards
Do not begin by alphabetizing one enormous box. First divide the collection according to how the cards are used. This prevents a complete deck from being treated as a source of loose copies and makes it immediately clear what players can borrow.
- Ready-to-play decks: Complete Corp and Runner decks that can be checked out without modification. Store each with its identity, decklist, format, revision date, and owner or library designation.
- Teaching decks: Stable introductory matchups kept separate from competitive or experimental decks. System Gateway is Null Signal Games' recommended entry point, and its card markings help reassemble the Starter Decks.
- Active deckbuilding pool: Loose cards legal in the format or formats your group builds most often. This should be the easiest zone to browse.
- Flex and testing cards: Extra copies, newly printed cards, possible swaps, and cards awaiting a deck decision. Keeping this zone small prevents temporary experiments from becoming permanent clutter.
- Archive: Rotated cards, superseded teaching materials, historical FFG-era cards, retired decklists, and anything the group wants to preserve without searching during routine deckbuilding.
Null Signal continues Netrunner following the end of Fantasy Flight Games' support, and its cards are designed to be interoperable with FFG-era Android: Netrunner cards. That does not mean every card belongs in the same current format. Interoperability concerns play; storage labels also need to communicate legality, source, and purpose.
Use a simple retrieval order for the active pool
Within the active deckbuilding pool, sort in the same order that players make deckbuilding decisions: side, faction, card type, then card name. Keep all available copies of a card together.
| Level | Recommended division | Why it helps |
|---|---|---|
| 1 | Runner or Corp | Prevents the most basic retrieval mistakes and mirrors deck construction. |
| 2 | Faction, with Neutral as its own section | Makes faction and influence decisions visible. |
| 3 | Card type | Reduces the area searched when looking for economy, ICE, breakers, agendas, or other deck functions. |
| 4 | Alphabetical by card name | Makes exact retrieval and return straightforward. |
| Separate section | Identities, tokens, reference cards, and backing cards | Keeps non-deck components from being filed as ordinary cards. |
Alphabetical sorting should be the final layer, not the entire system. A player usually knows that they need a Corp operation or a Runner program before they remember the exact card name. The hierarchy supports both browsing by role and retrieving a known card.
Set-based sorting is useful for archives and sealed teaching products, but it is slower for general deckbuilding. A practical compromise is to place a small set code on the divider or inventory record while keeping active cards grouped by faction and type.
Label physical source and image source separately
The word “original” is too ambiguous for a mixed collection. It might mean an FFG-era physical card, a finished Null Signal card, or a home print made from an official Null Signal file. Use two label fields instead: card-image source and physical production source.
| Collection category | Image source label | Physical source label | Suggested storage note |
|---|---|---|---|
| FFG-era physical card | FFG-era card | Commercial physical printing | Historical; verify current text and legality |
| Null Signal finished card | Null Signal card | Finished physical product | Check relevant current format |
| Official Null Signal PnP | Official Null Signal PnP PDF | Home or third-party print | Proxy; sleeve with an opaque back |
| Independent print | State the file or deck source | Independent printing method or service | Do not present as an official physical product |
This distinction remains accurate when an official print-and-play PDF is produced by a third-party printer: the face file can be official PnP while the physical card is not a finished Null Signal product. For production topics beyond Netrunner-specific setup, broader printing guidance may help, but collection labels should still identify unofficial physical prints transparently.
Null Signal offers both finished products and pay-what-you-want print-and-play PDFs, with fixed contents rather than randomized packs. NetrunnerAndroid is an independent deck and set printing service, not an affiliate of or service endorsed by Fantasy Flight Games or Null Signal Games. Those distinctions belong on box labels and inventory records, not only in purchasing notes.
Prepare print-and-play cards consistently
Null Signal's print-and-play faces are supplied without card backs. Its guidance is to place neatly cut faces in opaque sleeves with standard-sized game cards as backing cards. Consistent backing matters because a player should not be able to identify a card from its thickness, back, or movement during shuffling. See the practical guide to opaque sleeves, backing cards, and shuffle feel before assembling multiple decks.
Store spare backing cards, empty opaque sleeves, replacement faces, and a small number of labeled deck dividers together. That turns a damaged or revised card into a quick maintenance task rather than a reason to dismantle another deck. If the group produces its own files, check Netrunner card size, bleed, and safe-zone basics before committing to a large batch.
System Gateway provides both 1× and 3× PnP downloads; Null Signal describes the 3× files as a full playset of each card in that set. A playset is not automatically enough for a shared library. Two complete decks may need the same card simultaneously. Decide quantities from the decks your group wants to keep assembled, then add a small flex supply where overlap is common.
Track cards committed to decks
Shared staples create an availability problem rather than a sorting problem. If the box contains three copies but all three are in a checked-out deck, the loose-card inventory should show zero. Otherwise, another player may build a list that the library cannot supply.
A basic spreadsheet, index card, or shared document is enough. Record these fields for every maintained deck:
- Deck name and identity
- Corp or Runner
- Format and the date legality was last checked
- Decklist URL or saved list revision
- Borrower and checkout date
- Cards borrowed from another maintained deck
- Missing, damaged, or pending replacement cards
Choose one of two policies for high-demand cards. Either reserve copies for named ready decks, or treat every deck as temporary and return all cards after play. Mixing the two systems creates confusion because players cannot tell which deck boxes are safe to dismantle.
When a list becomes permanent, save its exact revision and mark it as assembled. When it is retired, return its cards to the active pool in one session and remove it from the checkout sheet. For the preceding file and list workflow, use the guide to printing a Netrunner deck from a decklist.
Keep formats separate without duplicating the whole filing system
Startup and Standard are distinct supported formats with different card pools and ban lists; Null Signal describes Standard as its flagship organized-play format. Because legality changes with releases, rotation, and policy updates, permanent handwritten claims such as “Standard legal” can age badly.
Use removable colored tabs or an inventory field rather than writing format legality directly on every card. One color can identify the group's primary active format, another can mark casual-only cards, and an archive divider can hold cards no longer used in either maintained pool. If your group is choosing its main environment, compare Standard and Startup before printing the pool.
Do not assume a deck is event-ready merely because every card came from the active box. Check the live Null Signal supported-formats page and the relevant ban list before organized play. Null Signal states that neatly cut home-printed proxies with opaque sleeves and backing cards are legal at its tournaments and events, but an independent organizer may publish additional requirements.
Maintain current text without replacing every older printing
An older physical card does not necessarily need to be discarded when wording or templating changes. Null Signal states that the authoritative current rules text is available through NetrunnerDB and that otherwise valid older printings do not need replacement solely because of wording changes.
For cards with meaningful text changes, place a small reference slip in the deck box or maintain a current-text list for the library. Avoid writing directly on historical cards. Replace a face only when readability, physical consistency, group preference, or an event requirement makes replacement the cleaner choice.
Use a short maintenance schedule
Review the library after a new set, rotation announcement, ban-list change, or major deck rebuild. A casual group can also schedule a quarterly check, but event preparation should trigger its own review regardless of the calendar.
- Confirm every ready deck still has the listed cards.
- Validate format and ban-list status against current Null Signal resources.
- Check NetrunnerDB for authoritative current card text where wording may have changed.
- Return abandoned testing cards to the active pool or archive.
- Replace damaged faces, split sleeves, and visibly inconsistent backing cards.
- Update checkout records and contact borrowers holding overdue decks.
- Move outdated format labels rather than leaving contradictory dividers in place.
- Keep FFG-era and other historical cards clearly identified without implying that age determines current legality.
The best system makes the next game easier
Start with the five zones, then sort only the active loose-card pool in detail. Keep ready and teaching decks intact, label print sources precisely, and track committed copies so availability is real rather than assumed. Finally, treat format legality and current card text as maintained information, not permanent properties of a box.
The practical next step is to empty one shelf, create the five zone labels, and classify every existing deck before touching the loose cards. Once complete decks are protected and archives are out of the way, the remaining Netrunner shared card pool storage job becomes a manageable retrieval system instead of a collection-wide excavation.