Factorio Blueprint Import Guide | Saving and Troubleshooting

Many players in Factorio 2.0/Space Age struggle when trying to import external blueprint strings – they paste them and lose track right afterwards, or they end up unsure where the blueprints have been saved. I hit the exact same wall at first, but once I separated the import entry point from the storage destination (inventory versus blueprint library), everything became much clearer.

This article is written for anyone who wants to reliably import code shared on distribution sites or in guides into their game, using Factorio 2.0/Space Age procedures as the standard. With the understanding that older 1.0/1.1 articles have UI differences, I've structured this to cover every failure pattern – from copy omissions to long character strings, DLC and mod dependencies, to Wayland pasting issues.

What Blueprint Import Can Do in Factorio

Blueprint import, in a nutshell, lets you take a design shared externally as a text string and bring it directly into your game. Whether the code is on a sharing site, sent by a friend on Discord, or elsewhere, in Factorio 2.0/Space Age you can paste it through the 'Import Code' option in the shortcut bar and it will load as a build plan. You don't have to rebuild it from scratch, so the payoff is especially large for highly reusable designs – standard starter lines, station templates, modularised smelters, and the like.

The key point here is that import is just the entry point into the game. Right after importing, you can place the blueprint immediately and use it, or if you want to reuse it later, you can move it to inventory or the blueprint library for storage. In other words, "loading" and "saving and managing" are separate operations, and once you think of them that way, the behaviour becomes much clearer.

This article assumes Factorio 2.0/Space Age as the baseline. While the blueprint concept itself is shared across older versions, you shouldn't apply UI positions and names directly – it'll only cause confusion. Especially for players coming back to the game, rather than hunting for it the way you remember from 1.0/1.1 articles, starting with the shortcut bar's 'Import Code' gives you a straight path forward.

The official Factorio Wiki confirms that blueprints can be exported and imported as strings, and that importing happens through a dedicated string-paste dialogue. Those long alphanumeric blocks you see in articles and sharing sites are just text to the eye, but the game interprets them as build information.

A little deeper into how it works: this string isn't meant for human reading – it's blueprint data converted to text. You don't need to understand the internal format to use it, but recognising that you're "carrying design data itself, not just a memo file" makes it easier to understand why copy errors or partial loss cause import failures.

I often paste strings my friends send me on Discord straight into 'Import Code' and use them in real gameplay. Especially for fiddly designs like station splits or oil processing where the shape is fixed but easy to misalign when building by hand – this flow is incredibly fast. When I get code from someone else and just paste it, the layout reproduces identically, making it easier to keep design philosophy aligned in multiplayer too.

For returning players especially, this route is the easiest to follow. Trying to learn B key library management all at once tends to lead to losing track of where things ended up. Instead, if you import from the shortcut bar first, place it, and then sort storage later if needed, breaking it into stages like this prevents getting stuck. I used to get lost on where to save too, but once I fixed the entry point, the operation suddenly made a lot of sense.

Background Knowledge: What Is a Blueprint String?

Terminology Clarification

Those long alphanumeric blocks you see in Factorio articles and sharing sites aren't just memos – they're blueprint text-converted sharing codes. A blueprint itself is a construction plan, but because the placement data, orientations, and connection information it holds can be written out as a string, when sharing with others, you're sharing "a string to reconstruct the blueprint" rather than "the blueprint itself".

The advantage is very straightforward. The receiver doesn't need to manually rebuild anything piece by piece – they just paste the string into the in-game import screen and the same design reproduces. When I distribute the station standard or smelter blocks I've made for mega bases, this string method is far faster than pictures or explanations. It looks like text, but it's actually design data – that's the core idea.

What's easy to confuse: "blueprint" and "blueprint string" aren't the same. A blueprint is the in-game construction plan itself; a blueprint string is how you carry it out externally or receive it. Sharing happens via string, but once it's in the game, you work with it as a normal blueprint.

In practice too, understanding this distinction makes troubleshooting much easier. If pasting doesn't work, you can think "the design isn't broken – the string is incomplete" or "the copy range was off" instead. Even if just the first character is cut off, import fails, so knowing the real nature helps a lot.

Where Do I Get Them?

In actual use, you're more likely to use codes someone else distributes than generate them yourself. The usual sources are external sharing sites like Factorioprints, Steam Community posts, personal blogs and Zenn articles, or friends pasting code on Discord. Station standards, starter research lines, oil processing, modularised smelters – highly reusable designs circulate this way.

The official Factorio Wiki confirms that blueprints can be exported and imported as strings. So using distributed codes is natural gameplay, not some hidden trick. When long strings appear inline in articles, they're not decoration – they're exactly what you paste.

From my experience, when I look at distribution sources, the important thing isn't "is the picture pretty" but "can I tell what this design is for?" and "what environment does it assume?". Whether it's vanilla, Space Age–based, or mod-dependent makes a huge difference to how useful it is. Distributions with explained design philosophy are much easier to reuse; ones with just the string alone are easy to misread the purpose of.

Also, understanding the string's true nature makes broken code easier to spot. I've had shared codes fail when chat app line breaks or quote marks snuck in during copy-paste. When you know "this isn't normal text – if even part of it is missing, it breaks", problem-solving becomes much faster.

Construction Plan - Factorio Wiki

wiki.factorio.com

The Technical Side (Base64/zlib/JSON) ※Beginners can skip

Looking at the technical level: blueprint strings aren't in a human-readable format. As explained in the Factorio Wiki's 'Blueprint string format', the string's content after the first character is expressed in Base64, which when expanded becomes zlib-compressed data, and decompressing that reveals JSON-based structure. Basically, design info is held in JSON, compressed, and made into a copy-friendly string.

You don't need to think about this structure during normal play – you can use it fine without understanding it. Just copy-paste and import. I rarely explain JSON to people I'm sharing with. The key point is simple: it looks like text, but inside it's structured data.

Understanding this does add up though. The reason stray characters in the middle break it is because it's encoded data, not plain text. Why the first character missing, the end being cut off, or quote marks and spaces mixed in cause import failures – all of that makes sense this way. Having a little analytical mindset makes it easier to judge "the game didn't mysteriously fail – the input data is corrupted".

For deeper dives into the technical side, Zenn's 'Let's analyse Factorio blueprints' is very clear with examples. You can see how placement data is stored, which is interesting if you want to really understand designs. But for the import task itself, you don't need to go that far. From a reader's perspective, knowing that your paste target is 'compressed design data', not 'mysterious text string' is enough.

Blueprint string format

wiki.factorio.com

How to Import Blueprints

The actual process is quite short: grab it from the shortcut bar and then save the blueprint that appears. The Factorio Wiki assumes blueprints can be imported as strings. I initially left the blue item that appeared right after pasting alone and thought "import failed" – it's easy to miss. The issue isn't the import itself but the save action after importing.

Step 1: Copy the String

First, copy the blueprint string from wherever it's distributed – just the string itself. The important part is getting only the blueprint string itself, not explanations or surrounding symbols. Sharing sites, Steam Community, blogs and other places often have explanations before and after the code block. If your copy range is even slightly off, import fails, so being conscious of whether you've got a continuous string from start to end helps prevent mistakes.

Long strings usually copy fine as-is. You don't need to reformat or add line breaks before pasting.

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

The shortcut bar's 'Import Code' option is a clear entry point for most players (you can also manage through the blueprint library). I'll note that the shortcut bar route tends to be less confusing as a starting point for imports, rather than going through the library side. For Factorio 2.0 / Space Age, thinking "check the shortcut bar first" is the most straightforward approach. Honestly, I also wasted time hunting on the library side after returning to the game.

Step 3: Paste the String into the Text Field and Press 'Import'

Paste the string you copied earlier into the window's text field and hit 'Import'. That's the whole operation. This is the basic flow you'll see described.

If nothing happens here, the problem is usually with the pasted string, not the in-game design. From my experience, most failures come from copy range misalignment or stray characters getting mixed in, not the design quality itself. As mentioned earlier, because this is data-not-text, even one character missing breaks it.

Blueprint - Factorio Wiki

wiki.factorio.com

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

When import succeeds, a blue blueprint item appears in your hand. This is the easy-to-miss part. Just loading isn't the end – you need to drag that blueprint into inventory for temporary storage.

Adding this one step cuts down accidental loss dramatically. For one-off testing of designs, inventory storage alone is plenty.

Step 5: For Frequent Use, Open the B Key Library for Permanent Storage

For designs you use repeatedly, opening the blueprint library with the B key and saving it there makes management much easier. You can open the library via the B key, buttons on the minimap, and it's handy for storing common designs – station standards, smelters, research lines and so on.

Operationally, import via the shortcut bar's 'Import Code' first, grab the appearing blueprint into inventory, then move it to the library. This flow is clearest. Single blueprints work fine in the library; multiple related ones fit better in a blueprint book. Designs made for reuse especially benefit from having a dedicated storage location – it cuts down on re-searching later.

Post-Import Storage and Management

Inventory Storage

Putting an imported blueprint into your inventory is temporary storage for immediate use within that save. Test placements of a new mining outpost, swapping out a current smelter, a temporary station template for your current work – if it's "I'm using this right now on this map", inventory is enough. You can grab it quickly and iterate on placement and upgrades, then keep a refined version going forward naturally.

However, inventory storage is really per-save hand management. If you dump every common design – stations, smelters, everything – into your hand inventory, you'll lose track of where you stored what. I used to do exactly that and ended up wasting time searching. Split it like: one-off designs stay in inventory, designs you reuse repeatedly go to the library next, and confusion drops way down.

Blueprint Library Storage

Designs you'll use long-term go much better in the blueprint library you open with the B key. The library isn't just a storage room – it's a repository for reuse across multiple saves. The Factorio Wiki's construction plan article treats blueprints as reusable design data, with that framework in mind.

The biggest payoff comes from designs that would be tedious to rebuild every time. Quad smelter lines, standardised station I/O, early power startup kits – things like that you can pull from the library instantly on a new save. Works great with quickbar placement and you can refine and update versions over time.

From my perspective, inventory storage is "the work bench on site" and library storage is "the blueprint originals in the design room". This distinction means you don't just import and call it done – you set yourself up to reuse easily next time without searching.

Organisation with Blueprint Books

Once blueprints pile up, bundling them into a blueprint book is far easier than lining up individual ones. Group them by theme – mining, rail, power, space – and you cut down steps to find what you need. If storage in the library is holding individual blueprints, books are the container that organises those contents systematically.

In practice, categorising designs by use keeps things clear. I split mine into three books – 'Mining Set', 'Station Templates', 'Space Platform Basics' – and it's incredibly stable. The Mining Set holds drill placements, poles, and belt takeoffs; the Station book holds one-way stations, sidings, fuel supply, and so on. This beats having tons of loose blueprints because "what goes where" becomes obvious.

Books give more than just search speed. You can bundle a whole set of designs needed for one outpost or process, so the startup sequence runs smoothly. Factory design is less about individual optimisation and more about whether you can hold related modules as a set. Books level up reusability in that sense.

Space Age especially leans on multi-planet, multi-platform operations, so blueprint management becomes more important. I haven't found official documentation on exact mechanics, so the cautions here come from user reports on forums and community articles. There are reports of inconvenience when boarding rockets with inventory, so I'd suggest pre-loading important blueprints to the library. A quick rundown: things you use right now stay in inventory, things you keep go to the library, related designs go in a book. Space Age operations really feel that organisation difference in speed.

The takeaway is simple: things for now go in inventory, keepers go to library, related stuff goes in a book. Space Age makes this difference in portability very real.

When Import Fails: Causes and Solutions

Copy Omissions, Whitespace, Quote Marks (" ", 『』): Checking

The most common import failures aren't game bugs – the string itself is slightly corrupted. Even if you thought you copied it from a share page, the start or end might be cut off, spaces or line breaks mixed in, or SNS and messenger use might turn quote marks into replacements. Marks like " " or 『』 are stray decoration, not part of the original string. These alone break import.

First thing I check: is the full string really selected, start to finish? Long strings cut off selection easily, and missing just the end isn't visible at a glance. Before pasting, I often run it through a text editor to check for leading/trailing space, line breaks, auto-converted quotes – that cuts diagnosis time. Pages wrap long strings in display, but that doesn't mean line breaks got added to the actual data, so removing unneeded breaks while keeping the original order is key.

The longer the string, the higher the risk of copy gaps and stray character addition. When paste doesn't work despite trying, honestly your best bet before investigating hard causes is re-copy the source and try pasting again. That solves it faster most times.

Version Mismatch, DLC/Mod Dependency

The string might be fine but made in a different environment – no match between versions and design. A classic is following old 1.1 era explanations with the 2.0 UI (UI positions and names being different between versions can mean "import option is nowhere to be found" and such confusion. Reference: Reddit post at [link] ). Designs relying on DLC or mods might not work in an environment without those, and whether you get rejected at import-time, placement-time, or can place but it won't function depends on the environment – advance testing is recommended.

The smart troubleshooting order: first check which Factorio generation the source assumed, then if Space Age is included or mods required. Because import success and design-actually-working are different problems with different root causes.

Wayland Pasting Failure on Linux and Workarounds

On Linux, handling large blueprint strings comes with a caveat: Wayland clipboard issues. The Factorio Wiki's version history notes that as of 1.1.0, very large blueprint string copy-paste problems and Linux Wayland clipboard behaviour mismatches had fixes recorded. This isn't just imagination – it's in the changelog.

From experience, 20-character-block scale sometimes looks unresponsive right after paste. My setup has times when waiting a few seconds lets it through, and times when going through another editor first is more stable. The longer the string, the more it looks like processing lag rather than actual failure.

Workarounds make sense to approach in stages rather than jump to special handling. First: re-copy clipboard and repaste; if that fails: send through a text editor to strip unneeded formatting, then paste. Additionally, Reddit's 'Alternative way to import blueprint' reports that X11 drag-and-drop worked, which while community-reported, makes solid sense – if clipboard pathways jam, switch to a different input method.

UI Nowhere to be Found

"I can't find the import location at all" is another common jam point. When this happens, look in the shortcut bar's 'Import Code' option, not the library management screen itself. Older guides and videos describe UI positions that differ from current perception, especially when you're following 1.1 era guides on 2.0 – easy to get lost.

Often it's not that features vanished but the shortcut bar state makes it invisible. Can't find buttons? Check if the shortcut bar is even visible – that alone often explains things. I originally hunted for an "import string" item inside the library itself and wasted time, but once I learned the entry is shortcut-bar-side, confusion dropped massively.

This type of problem usually isn't feature presence but looking in the wrong UI level. When stuck, teasing apart which bar the operation belongs to makes things clearer fast.

Shared String Corruption

If a received string is broken, the problem often isn't the source but the sharing pathway. Messengers, chat apps, and post forms sometimes truncate long text mid-way, auto-replace certain marks, add line breaks or quote styling. This transforms the sender's good code into something different on receipt.

Especially risky is when strings are formatted for readability – wrapping, quote blocks, machine translation, rich-text conversion – these don't mix well with blueprint strings. Seemingly minor text changes break machine parsing. When shared code won't paste no matter what, I often go back to the original distribution page or source and copy fresh. That's solved it most times.

The more sharing pathways the string goes through, the more risks: shortening, substitution, loss. To troubleshoot import failure, looking at where the string came through – not just copy mechanics – narrows causes significantly.

Tips for Using External Blueprints

Validate in a Test Environment First

Before dropping an external blueprint straight into your main factory, try it once in sandbox or the map editor. Reason's simple: copying success and design actually working are different. Especially with stations, smelters, circuits, rockets – prerequisites get complex. Visual inspection alone doesn't read requirements well.

I once pasted a station template straight into main base and jammed trains. The catch wasn't track count but signal logic – I didn't understand where trains wait, where they merge, what the signal design was actually controlling. After moving it to a test map and tracing train path reservations through signal placement, I finally got it: "this block separates to clear that section". Once that sank in, I could adapt the template to my actual track layout and keep things stable. Understanding before using means fewer jams and easier fixes when things break.

Older material like 'How to Play Factorio (ver 1.0)' from Zenn illustrates trying designs in alternate environments before bringing to main saves – still valid today. UI details and specific ops shift between versions, but the core troubleshooting flow hasn't aged.

How to Play Factorio (ver 1.0)

zenn.dev

Meet Prerequisites: Research, Materials, Terrain

Where external blueprints stall is often placeable but non-functional. This isn't import failure – it's missing prerequisites. Assemblers, inserters, belts, poles, signals lined up fine, but no go: unfinished required research, insufficient materials, wrong terrain. Any one breaks it.

Say you drop an advanced production line as-is – even with complete wiring, without unlocked machines or modules, construction robots won't finish it. Same goes for landfill-dependent coast designs or cliff-removal-included builds – geometry mismatch alone can break transport paths. Station templates might have track count right but insufficient approach space, too-short sidings for train length, or stacks that won't hold volume – all work-stoppers despite clean-looking placement.

Key bit is parsing "is this fixable by gathering more stuff?" versus "does the design's core concept not fit my situation?". Short on materials? Restock. Research or geography mismatched to your design? That blueprint is premature or planet-specific. Learning to swap machines, cut designs down, or redesign for your stage means treating external blueprints not as finished products but as componentised design assets.

Read the Design Intent

The real value in external blueprints isn't borrowing a finished product – it's experiencing the designer's reasoning. Why merge lines here? Why that ratio of assemblers? Why poles and signals in those positions? Understanding that transforms copy-paste-and-done into actual improvement and adaptability.

Production lines have set things to check. Input source and destination, compression points, overflow relief – those patterns repeat. Well-balanced designs have reasons for belt direction and inserter counts. Power also follows patterns: substation and medium pole placement isn't just supply coverage but set up for later sideways expansion. Circuit designs reward reading condition-checking over wire following.

The difference gets bigger with trains. I hit a wall on station templates until I quit seeing signals as "red-blue toggle parts". Once I understood path reservation separation, deadlock prevention at intersections, and stack overflow relief routes, the same template became adaptable to my actual network. Comprehension before deployment means fewer jams and capacity to self-repair.

The real breakpoint using external blueprints comes when you stop at "that's impressive" and start asking "why is that?". Once you're there, you can borrow someone else's designs while reshaping them for your own factory.

Common Questions

Where do I import from?

External blueprint strings come in through 'Import Code' on the shortcut bar at the bottom of the screen. Paste the string and import, and the blueprint loads immediately. When I first returned to the game, I wasted time hunting through the B key before remembering the import entry is the shortcut bar – things got smooth after that.

What's the difference from the B key?

The B key opens the Blueprint Library management screen. The Factorio the library accessible via B key or minimap buttons as the Blueprint Library. This location suits storage and organisation but has a different role from getting strings into the game initially. Think of it as: import via shortcut bar first, then move to library or book for management – that keeps confusion low.

Blueprint library

wiki.factorio.com

How does this compare to 1.1 era posts?

Older articles still offer useful thinking, but UI positions and labels don't always match 2.0. Particularly where 'import string' sits and how to access it need reworking from 1.1 screenshots. This article is based on Factorio 2.0 / Space Age procedures, so players stuck before because positions didn't match old guides will find navigation much easier once they clock the difference.

Does it work with Space Age?

Yes. Separate from Space Age content itself, blueprint import and library logic work exactly the same. Actually, bases split by function across planets, so organising blueprints in books – "smelting", "power", "stations" – is super handy. I reach a point where managing multiple outposts and holding books as units beats scattering single blueprints – it's dramatically simpler.

What if a long blueprint won't paste?

When a big blueprint string won't go in, try re-copying, stripping surrounding space and breaks, or pasting into a separate editor first then copying again. Diagnosis gets easier. Longer strings pick up stray characters from source pages or get trimmed mid-paste more often.

On Linux, Wayland clipboard issues have a known history of being patched, so pasting can jam in that channel. Standard copy-paste failing means the community has reported X11 drag-and-drop success. I couldn't find an official character cap, but very long code really does depend on input method – thinking of it that way keeps things organised.

Summary and Next Steps

Start by getting one short string through, doing the 'Import Code' → paste → import → save flow hands-on. That's the fastest way to learn. Once that works, move frequently-used designs to blueprint library or books and just check you've got the ingredients before placing – operations stabilise. When stuck, splitting by copy gaps, version/DLC mismatch, then long-text pasting narrows causes fast. The first success sets you up so the real game becomes storage and organisation, and getting that right boosts factory-building pace noticeably.

Next step is learning the view that turns borrowed designs into