How to Import Factorio Blueprints | Saving and Troubleshooting

In Factorio 2.0/Space Age, many players try to import external blueprint strings but lose them right after pasting or can't figure out where they've been stored. I hit the same wall early on, but once I understood the distinction between the import entry point and the storage destination (inventory vs. blueprint library), everything became much clearer.

This article covers step-by-step procedures for Factorio 2.0/Space Age, aimed at anyone who wants to reliably bring shared code into the game. Assuming UI differences from 1.0/1.1 articles, this guide walks through failure patterns—incomplete copies, oversized strings, DLC and Mod dependencies, and Wayland pasting issues—so you can troubleshoot each one.

What Blueprint Import Lets You Do

In one sentence, blueprint importing lets you take a design string shared externally and bring it directly into your game. Whether it's code posted on a sharing site, sent by a friend on Discord, or found elsewhere, in Factorio 2.0/Space Age you can paste it through the shortcut bar's 'Import Code' button and load it as a construction plan. You don't have to rebuild from scratch, so frequently-reused designs—early-game production chains, standardized stations, modular smelters—pay huge dividends.

The key point is that importing is just the entry point into the game. Right after importing, you can place it immediately, or move it to inventory or the blueprint library for later use. In other words, "loading" and "saving and managing" are separate steps, and separating them this way makes behavior much easier to understand.

This article covers Factorio 2.0/Space Age as the baseline. Blueprint concepts carry over from older versions, but UI positions and terminology don't map directly—don't assume they do. Players returning to the game especially benefit from starting with shortcut bar 'Import Code' rather than hunting through old 1.0/1.1 memories.

The official Factorio Wiki's 'Construction Planner' confirms blueprints can be exported and imported as strings, and that importing happens through a text-paste dialog. The long alphanumeric blocks you see posted in articles or sharing sites aren't just decoration—they're what you paste.

Zooming out a tiny bit on the mechanics: this string isn't human-readable text; it's blueprint data converted to text form. You don't need to know the internals to use it, but understanding "this is design data being transported, not a memo" makes sense of copy losses or partial corruptions.

I often receive station blueprints from friends on Discord and paste them straight into 'Import Code' for real-world testing. Especially with designs like rail junctions or oil fields—layouts that are fixed but easy to misalign by hand—this flow is incredibly fast. Taking the code and pasting it directly recreates the same layout, so multiplayer bases stay architecturally aligned too.

This path is clearest for returning players. Trying to learn B-key library management all at once is a recipe for losing track of where things landed. Breaking it into stages—import and place first, organize the storage location later—prevents getting stuck. I was lost on storage at first, but pinning down the entry point made the intent crystal clear.

Background: What Is a Blueprint String?

Terminology

The long alphanumeric blocks found in articles or sharing sites aren't just notes—they're blueprint data converted to shareable text. A blueprint itself is a construction plan, but since you can write out its placement, rotation, and connection info as a string, sharing works by transmitting "the string that restores the design" rather than "the design itself."

The payoff is straightforward: the receiver doesn't rebuild piece by piece. Paste into the import screen, and the same layout materializes. When I distribute a megabase station standard or smelter module, this string method beats pictures or descriptions by a landslide. Text on the surface, design data underneath—that's the mental model.

The easy confusion: "blueprint" and "blueprint string" aren't interchangeable. The blueprint is the in-game design itself; the blueprint string is how you port it out or receive it. Sharing starts as text, but once in-game it's a normal blueprint again.

In practice, knowing this distinction helps with troubleshooting. If pasting fails, you ask "is the design wrong?" or "is the string corrupted?" Once you know the difference, you spot that a single missing character at the start breaks everything—a useful insight.

Where Do I Get Them?

Most of the time you're copying distributed code rather than generating your own. Common sources: Factorioprints (external sharing site), Steam Community posts, personal blogs, Discord friends. Designs with high reuse—station standards, early production chains, oil processing, modularized smelters—circulate this way most.

The official Wiki's 'Construction Planner' confirms blueprints can be shared via string. So using external code is a natural feature, not a workaround. When articles include long character blocks inline, that's the paste target—not decorative.

From my experience, what matters when reviewing a source: "Is the layout clean?" matters less than "What's this for?" and "What environment is assumed?" A barebones design or Space Age–dependent placements will matter differently than vanilla setups. Well-documented distributions are reusable; strings-only posts are easy to misinterpret.

Also, slight familiarity with the format itself makes spotting broken codes easier. I've pasted shared strings and had chat app line breaks or quote marks sneak in and corrupt them. Knowing "this is not normal text; any breakage fails the load" speeds up diagnosing the issue.

Blueprint - Factorio Wiki

wiki.factorio.com

The Technical Stuff: Base64/zlib/JSON (Readers Can Skip)

Looking deeper, the blueprint string is not in human-readable form. Per Factorio Wiki's 'Blueprint string format', the text minus the first character is Base64, which when expanded is zlib-compressed data that decompresses to JSON-based structure. So the design is held in JSON, compressed for copyability, then encoded to text.

You don't need this perspective during normal play—pasting and importing works fine without it. I rarely mention JSON when sharing with others. The single takeaway: "text appearance, but internally structured data."

Knowing it helps things click: a stray character mid-string breaks it because it's encoded data, not plain prose. A missing first character, truncated end, mixed quotes, or whitespace garbles it—these fail for cause, not whimsy. A little analytic mindset shifts "the game glitched" to "the input data broke."

Want to dig deeper? Zenn's '【factorio】ブループリント解析してみた' walks through real examples of how placement gets encoded. Neat if you want deep design literacy. But for importing purposes, understanding "the target is compressed design data, not a meme text file" suffices.

Blueprint string format

wiki.factorio.com

How to Import a Blueprint

The actual workflow is short: grab the code from the shortcut bar, paste, and save the result. The 'Construction Planner' Wiki article assumes strings can be imported this way. I initially thought the blue item appearing after paste meant failure and got confused. The hiccup isn't the import itself—it's what you do with the imported blueprint after.

Step 1: Copy the String

Start by copying the blueprint string from its source as-is. The critical part: grab only the blueprint string itself, not surrounding explanation or symbols. Sharing sites, Steam posts, or blogs often frame the code block with text. A slight copy misalignment kills import success, so check that the beginning-to-end selection is clean and continuous.

Long strings paste fine as-is normally. No need to pre-format or inject line breaks.

Step 2: Open 'Import Code' from the Shortcut Bar at Screen Bottom

For most players, the shortcut bar's 'Import Code' button is the clearest entry (blueprint library imports are also possible, but shortcut bar is less confusing for first-timers). Old articles sometimes show UI in different places, but Factorio 2.0 / Space Age baseline says start at the shortcut bar. Fresh returnees like me used to hunt through the library instead—a detour.

Step 3: Paste into the Text Field and Click 'Import'

Paste the copied string into the dialog's text box and press 'Import'. That's the move. 'How to Import Blueprints' runs through this same basic flow.

If nothing happens, the culprit is almost always the pasted string, not the design itself. From my track record, failures stem from copy range gaps or stray character creep, not design quality. As noted above, this is data-like, so even one character slip breaks it.

Blueprint - Factorio Wiki

wiki.factorio.com

Step 4: Drag the Resulting Blueprint into Inventory for Temporary Storage

After import succeeds, a blue blueprint item appears in your hand. This is the easy-to-miss part. A loaded blueprint doesn't mean organization is done—you need to drag it into inventory to hold onto it.

This single extra step cuts the "where did it go?" accidents dramatically. A one-off test? Inventory storage is fine.

Step 5: For Frequent Use, Press B to Open Library and Archive Long-Term

Designs you'll reuse repeatedly? Open the Blueprint Library with B key and store them permanently. The library, accessible via B key or minimap button, is your archive for go-to layouts—stations, smelters, starter power setups. It beats keeping everything loose.

The workflow: import via shortcut 'Import Code', secure the blueprint in inventory, then move to library. Single blueprints stay in the library; related groups go in a book. Especially for reuse-focused designs, pick a storage home so you're not re-searching later.

Storage and Organization After Import

Inventory Storage

Putting the post-import blueprint in inventory is storage for immediate, same-save use. Mining outpost test, smelter swap, station template trial—"I need this now on this map"—inventory is enough. Instant access, quick place-and-tweak, then keep the revised version: natural flow.

But inventory storage is same-save, short-term only. Dumping every reusable standard there gets messy; you'll hunt forever. I mixed station and smelter templates in my hand items early and regretted the search time after. Splitting it—current session stuff in inventory, repeatable designs in library—prevents confusion.

Blueprint Library Storage

Long-term designs move to the Blueprint Library (B key open). This isn't just a bucket; it's a reuse archive spanning saves. The Wiki's 'Construction Planner' frames blueprints as reusable design data across worlds.

The big win: standard builds you'd rather not rebuild each session. Four-line smelter, station in/out, starter power setup—plunk them in library and spin up new saves with instant access. Quickbar placement pairs well, and you iterate versions while keeping the library copy current.

My mental model: inventory is "the work desk," library is "the design archives." Drawing that boundary makes fresh saves pull pre-solved layouts, not one-offs.

Blueprint Books for Organization

When blueprints pile up, packing them into blueprint books beats scattered singles. Mining, rails, power, space stuff—group by theme, and reaching the design you want takes fewer clicks. If library storage is "archive," books are "organized file cabinets within the archive."

Operationally, thematizing blueprints cuts confusion. I keep 'Mining Sets', 'Station Templates', and 'Space Platform Basics'—three books. Mining sets hold extractor configs, poles, and belt pulls. Stations hold one-way, sidings, refueling. This beats sprawling blueprints; "where did I put this?" becomes obvious.

Bookmarking helps beyond search. Designs needed for a stage or outpost group together, so startup flows align. Factory design is less about individual optimization and more about whether you have related modules as sets. Books lift reuse up a level.

Space Age tilts this harder: multi-planet operations make blueprint management more crucial. Since official specs don't detail hand-item carry across planets clearly, user reports suggest keeping critical blueprints pre-booked in library. Load time parity between saves works better than juggling hands.

The rule of thumb: current-session stuff in inventory, keepers in library, related groups in books. Space Age makes this triage pay off fast.

Why Imports Fail—and How to Fix Them

Missing Characters, Whitespace, Quote Mark Creep

The most common import failure is the string itself got mangled, not an in-game glitch. Copied from a share page but missing start/end, whitespace/line breaks mixed in, SNS or messenger apps auto-converting " " or 『』—these wreck import. Stray decoration marks that weren't in the original stop the whole thing.

My first check: Is the full string selected start-to-finish? Long strings truncate easily mid-select, invisible at the paste stage. Before pasting, dump it into a text editor and inspect the start, end, whitespace, and auto-conversions. Strip unneeded line breaks while keeping the original line order—that's the balance.

Longer strings fail more often from copy truncation or stray-character insertion. Pasting to an import screen with no response? Rebest approach: recopy the original and repaste. Solving this usually beats chasing harder causes.

Version Gaps and DLC/Mod Dependency Sorting

String health is fine, but if the context differs, layout won't match. Typical: old 1.1 guides read in 2.0 UI, or 2.0/Space Age designs in older clients (version gaps cause "import UI is missing," "location described doesn't exist"—see Reddit discussion). Or DLC/Mod-dependent entities in a base install—they import but don't function or won't place, depending on environment.

Sorting order: What Factorio version does the source assume? Next, Is Space Age/DLC or Mod foundation required? This separates "import machinery issue" from "missing pieces to run the design," which are different root causes.

Wayland Paste Hiccup and Workarounds on Linux

Long blueprint strings on Linux hit Wayland clipboard trouble sometimes. Factorio Wiki's 'Version history' logs that version 1.1.0 fixed very-long-string copy/paste bugs and Wayland clipboard mismatches. So this isn't paranoia; it's a documented thing.

Anecdotally, 20-character-class strings go unresponsive-looking post-paste. In my environment, waiting a few seconds works sometimes; other times a text-editor detour runs smoother. Longer input = heavier lifting = sometimes it looks frozen.

Escalation path: try recopying and repasting first. If stuck, paste to a text editor to strip formatting, then repaste. Bonus: per Reddit's 'Alternative way to import blueprint', X11 drag-and-drop bypassed clipboard issues for some. Community-sourced, yes, but the "switch pathways if clipboard jams" logic is sound.

UI Nowhere to Be Found

"Import dialog doesn't exist" is a real jam. Look for import at the shortcut bar's 'Import Code button—not the library screen itself. Old articles or videos misdirect because 1.1 layout differs from 2.0. Pairing old docs with 2.0 gameplay confuses fast.

The hidden culprit is often shortcut bar visibility, not missing features. Buttons out of sight mean the bar isn't showing, not that import vanished. I initially hunted inside library for a direct import option and took the long way. Once I knew the entry was shortcut bar–based, no more loops.

These snags are usually UI position miscues, not features gone missing. Stuck finding something? Which bar is the control on? Answering that usually settles it.

Shared String Corruption in Transit

Received strings can break in transit, not at the source. Messengers, chat, form fields—they truncate mid-text, auto-swap symbols, pad with brackets, or reflow as rich text. None of this wrecks normal emails, but blueprint strings break instantly.

Risky: polished-looking shares. Reflowing, blockquoting, web-translating, rich-text converting—all hostile to blueprint format. Small edits, huge impact. When pasting shared code over and over fails, I backtrack to the original source or config file rather than recopying the message. Upstream usually works.

Each share hop multiplies risk: truncation, swap, dropout. Fault-finding? Trace which path the string took. Upstream source beats recopied intermediaries—hunt the root.

Tips for Using External Blueprints

Test Drive in Sandbox First

External blueprints work better in test environment (sandbox or map editor) before live deployment. The reason: pasteable ≠ functional. Especially complex designs—stations, smelters, circuits, rockets—have requirements not obvious from sight.

I once threw a station template straight into my megabase and jammed up trains. Turned out the signal split/merge logic I didn't read prevented forward motion. Pasting into a test map, watching train pathfinding flash red/blue under the signals, I finally grasped "oh, it separates here so cars don't clog the merge." Only then did live placement work smoothly. Understand before deploy; repairs flow naturally after.

The old 'Factorio beginner's guide (ver 1.0)' approach—one environment to trial, another to go live—still holds. UI moved, but the validation workflow hasn't aged.

Factorio beginner's guide (ver 1.0))

zenn.dev

Verify Research, Materials, Terrain Prerequisites

Designs trip up frequently as "placed but idle" situations. Parts sit there but nothing runs because prerequisites—unreleased machines, missing materials, incompatible terrain, wrong power state—aren't met.

Example: fancy production line, placed in full. But the target machine is locked behind unresearched techs. Robots can't finish. Shoreline designs assuming landfill or cliffs assume geology shifts. Rail stations assume incoming track orientation, platform span, or stack length match. Mismatch in any prerequisite—research, items, terrain, power—and the design stalls.

The fix: before tweaking, what's actually missing? Are materials collectible (fixable) or is the design fundamentally early for your stage (not ready yet)? Terrain or tech gating? If design hinges on unfulfilled preconditions, it's not yet applicable; maybe it's for another planet. Scaling down parts or swapping gear—that's how borrowed designs become personal assets, not copy-paste duplicates.

Read the Designer's Logic

External blueprints' true value isn't the finished product—it's watching how the builder thought. Why merge here, not there? Why that ratio of assemblers? Why poles and signal rows in those spots? Chase that logic, and reuse becomes improvement.

Production lines have tells. Input source, compression points, excess escape route. Balanced designs have machine counts for reason. Power setup plays out similar: pole range plus later horizontal expansion aren't accidents; they're intent. Circuit-heavy builds? Read the stop condition, not just wiring.

Train designs amplify this leverage. Our station template failure was me reading signals as "red-blue toggle part" instead of "path-reserve blocker." Watching where trains reserve track, where stacks bleed exits, how merges avoid gridlock—once I chased that intent, same template became adjustable to my rail net. Understand before use = adapt on demand, not break-and-repair.

Borrowed designs shift from "neat" to "game-changing" the moment you ask "why is it this way?" That gap is where expertise lives.

Frequently Asked Questions

Where do I import from?

External blueprint strings come in through the 'Import Code' button on the shortcut bar at screen bottom. Paste the string and hit import—the blueprint loads instantly. When I first came back, I hunted through the B key side for a while, but once I locked in that the import entrance is the shortcut bar, things got smooth fast.

What's the difference between importing and the B key?

The B key opens the Blueprint Library management screen. Factorio Wiki treats the library (accessible via B key or minimap) as an archive and organization tool. But it's separate from the import operation itself—that initial feed of strings into the game. Think: shortcut bar imports first, then library/book afterward for long-term storage. Separating those phases kills confusion.

Blueprint library

wiki.factorio.com

How does this differ from old 1.1 guides?

Older articles have good foundations, but UI position and labels aren't 2.0-consistent. The location of "import string" and where to trigger it often require reframing for 1.1 docs. This article is grounded in Factorio 2.0 / Space Age steps, so players stuck because old-guide locations didn't match 2.0 reality will find clarity once they absorb those UI shifts.

Does it work in Space Age?

Absolutely. Beyond Space Age content itself, blueprint import and library workflow carry over as-is. Better yet: planets naturally segment base roles, so organizing via books—'smelting,' 'power,' 'stations'—is super handy. Once I hit multi-base scale, single scattered blueprints felt chaotic next to book-grouped management.

What if I can't paste long blueprint strings?

When a long string refuses: try recopy, strip leading/trailing whitespace and line breaks, paste to a text editor first, then copy again. Longer text = more stray chars at source, more truncation mid-paste. Linux Wayland has clipboard history—pasting there can jam. If standard copy/paste stalls, X11 drag-and-drop got reported working. No official character ceiling found, but huge blueprints are input-path sensitive—that framing helps troubleshoot. Just separating "B key search" from "shortcut bar input" cuts import snags way down.

Wrap-Up and Next Steps

Start with a short test string, walk through 'Import Code' → paste → import → save. Once that works, move frequently-used designs to library or books, and pre-check if prerequisites line up before placement—operations stabilize. Stuck? Chase copy gaps, version/DLC mismatches, then long-string paste issues, in that order—root cause clears fast. Hitting that first win shifts focus from import to save and organize. Nailing that polish alone speeds factory-building tempo significantly.

Next level: taking imported designs and "making them yours." Understanding creation fundamentals plus book organization lets borrowed blueprints grow into personal infrastructure. That's where the real leverage lands.