How to make Fortnite in Infinite Craft: full recipe

How to make Fortnite in Infinite Craft: a recipe path and what each step really means

The shortest path to make Fortnite in Infinite Craft runs through a chain of small element combinations, and the most useful thing a player can do is understand the order, the reason behind each merge, and the branches that look correct but fail. The game is a sandbox built by Neal Agarwal in which the player drags two visible elements onto a workspace and the engine tries to combine them. The result is either a new element or nothing, and over thousands of attempts the community has mapped the branches that lead from the four starting elements (Earth, Water, Fire, Wind) to recognizable real-world concepts. Fortnite is one of those late-chain concepts, and reaching it depends on a few specific combinations that the engine accepts, plus a careful interpretation of what the on-screen label actually represents.

This guide treats the recipe as a design problem rather than a trivia answer. The focus is the chain a player needs to follow, the alternative routes when a step fails to resolve, the visual language the game uses for its named elements, and a small set of practical habits that make long chains more reliable. None of the steps require skill beyond dragging and dropping, but reading the chain correctly is the difference between finishing it in a few minutes and getting stuck on a label that looks right but never accepts another input.

What Infinite Craft actually does when two elements combine

Before walking the Fortnite recipe, it helps to understand the small amount of engineering behind the toy. Infinite Craft is a browser game that runs entirely in the page: a JavaScript engine holds the player’s discovered elements, checks the pair against an internal recipe table, and either returns a new element or nothing. The visible reaction is a small animation and a label that drops into the “Discoveries” panel on the right. There is no offline state to sync, no login required, and the entire library of possible results is fixed by the author, even if the community has not yet documented all of them.

The engine pairs elements by their stored identifier, not by what the label looks like. That is the single most important habit to develop: if the visible name of an element seems to imply a concept that would combine in a sensible way, the engine may still reject the merge because the stored entry is keyed under a different concept. The common symptom is a pair that looks like it should make something interesting, but the drop animation shows the two elements bouncing back to the panel without a new discovery. The pair is not wrong in a story sense; the engine simply has no entry for that exact combination.

Three practical habits follow from this:

Treat each label as the engine’s own private name, not as a free-form word. Two labels that share a concept may not be interchangeable.
When the engine rejects a pair, move the rejected element aside and try the same target with a nearby cousin from a previous discovery. The same destination often has two viable parents.
Keep the recipe path written down or open in a second tab. The discoveries panel is searchable, but it does not show the parents of a result, so reconstructing a chain from memory is slow.

The recipe below is the most consistently reported path, and the rest of the guide explains the order, the alternatives, and the interpretation of each intermediate result.

The full recipe path from start to Fortnite

The chain below is the shortest practical path that the community has verified. The arrow shows the two inputs on the left that produce the new element on the right. Every node except the four starting elements is created by the player; if any step fails, jump to the “Branches and fallbacks” section below.

Step	Combine	Result	Why this step works in the engine
1	Water + Water	Lake	The engine treats two identical water elements as a doubled body of water and names the result Lake.
2	Lake + Water	Ocean	Adding a third water parent escalates the result to Ocean, the largest conventional water body in the engine’s vocabulary.
3	Earth + Water	Plant	A foundational combination. The engine reads Earth and Water as the two ingredients for living vegetation.
4	Plant + Earth	Tree	Adding Earth to a Plant produces Tree, a frequent parent for any later result involving wood, forest, or shade.
5	Tree + Tree	Forest	Two Trees resolve to Forest. This element becomes a hub for any later branches about nature, wildlife, or rural settings.
6	Forest + Lake	River	A Forest plus a Lake combines the natural container of water with a wooded setting and produces River.
7	River + Wind	Steam	Wind acting on a River is interpreted as kinetic energy, and Steam is the engine’s vocabulary for moving vapor.
8	Steam + Earth	Geyser	Earth plus pressurised Steam produces Geyser, a natural hot spring that the engine uses as a step toward volcanic and energetic features.
9	Geyser + Earth	Volcano	Adding Earth to a Geyser escalates the natural feature into Volcano, one of the most useful intermediates in the game because it is a parent for several high-level concepts.
10	Volcano + Water	Stone	Water and lava produce cooled volcanic rock. The engine names this result Stone, which becomes a parent for tools, masonry, and eventually the next step.
11	Stone + Fire	Metal	Fire applied to Stone produces Metal, the engine’s way of saying smelted rock. Metal is the parent for weapons, tools, and most industrial chains.
12	Metal + Stone	Blade	Two hard materials combine into Blade, a frequent parent for weapons and combat.
13	Blade + Metal	Sword	The engine escalates Blade plus Metal into the named weapon Sword.
14	Sword + Sword	Duel	Two weapons together produce Duel, an abstract concept that the engine treats as the parent for combat culture and its fiction.
15	Duel + Forest	Battle	Adding a Forest to Duel elevates the conflict to Battle, a concept tied to a place and a clash rather than a personal encounter.
16	Battle + Volcano	War	The combination of Battle with a destructive geographic feature produces War, a high-level abstract result.
17	War + Forest	Battle Royale	Forest added to War produces the named genre Battle Royale, the conceptual parent for Fortnite in this chain.
18	Battle Royale + Building	Fortnite	Building is reached separately and combined with Battle Royale to produce the final result Fortnite. The label is the in-game name of the Epic Games title, and the engine accepts this combination as the last step.

Step 18 assumes the player has already created Building through its own short chain. The next section shows how to get there with the fewest intermediate elements.

How to reach Building for the final merge

Building is a required parent for the last step. There are several recipes, and the most reliable one for new players is the workmanlike path through tools, wood, and shelter. The order is small enough to finish before the long chain above, and every intermediate element is reused by other recipes, so nothing is wasted.

Step	Combine	Result	Why it works
1	Earth + Fire	Lava	The engine reads heat applied to ground as molten rock and labels it Lava.
2	Lava + Water	Stone	Cooling lava produces Stone, the same intermediate reached in the main chain. If Stone is already discovered, this step can be skipped.
3	Stone + Wind	Sand	Erosion by wind on stone produces Sand.
4	Sand + Fire	Glass	Heat applied to Sand produces Glass.
5	Stone + Fire	Metal	The same smelt Stone that produced Glass. If Metal is already in the discoveries panel, skip this step.
6	Metal + Stone	Blade	Same intermediate as the main chain. Reuse is free.
7	Tree + Blade	Wood	The engine accepts Tree plus Blade as processed timber and labels it Wood.
8	Wood + Wood	Wall	Two pieces of timber resolve to Wall.
9	Wall + Wall	House	Two walls form a House, a useful parent on its own.
10	House + Wood	Building	Wood added to House produces the abstract result Building, which is the second parent for the final Fortnite merge.

Once Building is in the discoveries panel, the player only needs to combine it with Battle Royale to finish the recipe. The full chain involves roughly 28 unique elements when the two branches share intermediates, and the run is usually under 15 minutes from a clean start if the player keeps the chain on a single page.

Branches and fallbacks when a step fails

Recipes in Infinite Craft are not guaranteed on every player’s account. The engine is consistent for a given browser at a given moment, but small differences in the recipe table have been reported over the lifetime of the game. The list below shows the most common stuck points and the alternative parents that usually work.

If Lake plus Water does not produce Ocean, try Lake plus Lake instead. Some versions of the engine resolve two lakes to a Sea, and Sea plus Water returns to Ocean.
If Plant plus Earth fails to produce Tree, retry with Plant plus Plant. Two plants sometimes escalate to Tree directly when the Earth parent is locked behind another recipe.
If Tree plus Tree does not give Forest, try Tree plus Wind for a different kind of escalation, then combine the new result with Earth. The path is longer but is a documented fallback.
If River plus Wind does not produce Steam, try Ocean plus Fire. Ocean and fire are accepted as Steam in some versions and reach the same downstream results.
If Stone plus Fire does not produce Metal, try Stone plus Stone for a second Stone, then Stone plus Earth. Earth plus Stone has been reported as a Metal path in older versions.
If Sword plus Sword does not produce Duel, try Sword plus Battle. The result is still Duel, and the engine sometimes resolves the abstraction more cleanly with a parent that already has combat meaning.
If Battle Royale plus Building does not produce Fortnite, the most common cause is that the player’s local engine resolves Battle Royale to a different label, such as Last Man Standing or simply Royale. The player should open the discoveries panel, search for “Fortnite” in case the result was reached through an undocumented parent, and try a Battle Royale plus Sword combination as a final fallback.

Each fallback costs only a few seconds, and the engine does not penalize failed attempts. The Discoveries panel keeps every intermediate result the player has ever made, so failed branches do not set the player back; they only clutter the panel slightly.

What the Fortnite result actually represents in the engine

Once the result lands in the Discoveries panel, the engine treats it like any other high-level element. It can be combined with other results to produce further named concepts, and the player’s path through those combinations is part of the long tail of the game. Two observations about the Fortnite result are worth understanding before treating it as a final destination.

First, the label is the engine’s stored name for the Epic Games title. The game does not have licensing rights to use any actual game asset, and the on-screen result is a text label that behaves like a normal element. There is no embedded video, no playable mini-game, and no link to the real product. Players who have seen videos that show a playable Fortnite in Infinite Craft are looking at edited previews, not a feature of the live browser game. The cultural weight of the label is what the engine actually stores; the visual identity of the franchise is not part of the chain.

Second, Fortnite is a useful parent for several other late-game results. The engine has been documented to accept combinations that produce adjacent concepts in the same cultural space, and Fortnite often sits near them. The exact list varies as the author updates the recipe table, so a player who reaches Fortnite should treat it as a waypoint rather than the end of the chain. For background on the broader game itself, including its battle royale format and the building mechanics that the Infinite Craft result is named after, the Fortnite overview on Wikipedia covers the production history, the standalone modes, and the long-running Save the World campaign that the sandbox chain never tries to represent.

Practical tips for running long chains cleanly

Long chains like the one above are easy to break by accident, and the engine does not warn when a player deletes or replaces an intermediate. The following habits make the chain repeatable.

Open the game in a single tab and leave it open. The discoveries panel and the recipe path share the same in-memory state, and a refresh restores the same data, but switching devices or browsers starts a fresh library.
Drag finished intermediates to the right side of the workspace so they are not under the cursor. Two active elements next to each other invite accidental drops.
Name the work area mentally: keep the current “active” parents at the top, push completed intermediates into a clean column, and reserve the bottom for the final targets like Battle Royale and Building.
Use the search bar in the Discoveries panel rather than scrolling. The panel holds every result the player has made, and the search is case-insensitive and partial-match.
If a step fails twice with the same parents, stop and try a cousin. The engine is deterministic, and a third attempt with the same inputs will fail the same way.

These habits are not required, but they reduce the cognitive load of running a 25-step chain in a single sitting, especially for players who run the recipe in multiple browser sessions. A second pass on the same chain usually takes half the time of the first because the player stops hovering over the wrong parents and starts moving them with intent.

Why this recipe is the most reliable path

Infinite Craft has thousands of documented combinations, and Fortnite has multiple potential chains. The path above is the most reliable for three reasons. First, every intermediate result except Battle Royale and Building is reachable through small steps that the engine almost always resolves. Second, the chain reuses elements that the player has likely already discovered, so the time cost of a second run is closer to 5 minutes than 15. Third, the parent concepts move from concrete to abstract in a clear narrative: water to lake, lake to ocean, plant to tree, tree to forest, and so on. That progression is closer to how the engine’s author appears to have designed the table than the abrupt shortcuts some online lists suggest, and it tends to age better as the table is updated.

Shorter paths do exist in some versions, often by skipping Volcano or Battle, but they depend on recipe table entries that have not been stable across the game’s history. The 28-element chain is the version a new player can complete on a first try without referring back to a fallback list. A useful side benefit is that most of the intermediates are themselves parents for other late-game results, so the time spent on the chain pays off the next time the player sits down with a different target.

Common mistakes that look correct but fail

The single most expensive mistake is treating two visible labels as interchangeable when the engine stores them under different concepts. The visible game, the engine’s internal name, and the player’s intuition can disagree, and only the first two matter. A small set of labels is responsible for most of the confusion on this chain.

Sea vs. Lake vs. Ocean. The engine treats these as separate results. Reaching the next step requires the exact label documented in the recipe, not a synonym that the player discovered earlier.
Fire vs. Lava vs. Steam. All three are heat-related, but the engine only accepts one of them as the parent for the next step in any given branch. Picking the wrong one stops the chain without an obvious error.
Wood vs. Tree vs. Forest. Each is a distinct result. Substituting one for the other looks reasonable but never resolves to the next element on the chain.
Battle vs. Duel vs. War. These are all combat-related results, but the engine uses them in a specific order. Duel is personal combat, Battle is a place-bound clash, and War is the abstract escalation. Skipping Duel breaks the chain in some versions of the engine.
Building vs. House vs. Wall. Building is a higher-level abstract result than House, and House is a higher-level result than Wall. Using the wrong one means the final step finds no matching recipe.

If a step fails twice, the cause is almost always one of the substitutions above. The fastest recovery is to recreate the missing parent from a known earlier step rather than guessing a new parent from the panel. Players who try to substitute synonyms because the recipe list feels verbose usually end up restarting the chain from the closest stable intermediate, and that is faster than chasing dead ends through the Discoveries panel.

How long the chain takes and what slows it down

A clean first run takes about 12 to 15 minutes for a player who has never used the game before and reads each step. A player with the four starting elements in the panel and a clear workspace can finish the same chain in under 5 minutes. The two factors that slow the chain the most are misclicks during the final Building step, where the player accidentally combines Building with a sibling like Wall instead of dragging it cleanly to Battle Royale, and repeated failures on a stuck parent, where the player retries the same combination instead of moving to a documented fallback.

The Discoveries panel can hold thousands of entries on a long account, and the search bar is the only practical way to navigate it. Players who plan to run several long chains should get used to the search bar before they start a recipe rather than after they have lost the parent they need. A useful benchmark is that any chain which takes longer than 20 minutes is almost certainly failing on a label substitution, not on a real engine bug, because the table resolves quickly when the parents are clean.

What to do after reaching Fortnite

Fortnite is a valid parent for several additional results, and the engine has been documented to produce further named concepts when it is combined with a few other late-game elements. The exact list depends on the current recipe table, so the practical recommendation is to open the Discoveries panel, search for “Fortnite”, drag it onto the workspace, and try it against any other late-game element the player has discovered. Each successful combination becomes a new entry, and the engine does not cap the total number of discoveries.

For developers and curious players, this is also the moment where the toy stops being a recipe and starts being a graph. A player can export the discoveries list, write a small script to count the unique parents of a given element, or compare two recipe tables to see how the author has changed the engine between versions. Infinite Craft has no official API, but the discoveries panel is a static HTML list, and a player with developer tooling can capture it cleanly. The most interesting findings tend to be the unexpected late-game results, where two unrelated concepts combine into a single label that has no obvious parents on the chain the player just walked.

How the chain compares to other late-game targets

Fortnite is one of several late-game results that share the same combat-and-culture vocabulary, and the chain is similar in shape to other popular targets like Minecraft, Call of Duty, or League of Legends. Each of those results needs a genre parent (Battle Royale, First-Person Shooter, MOBA) and a platform or medium parent (Building, Gun, Champion), and each follows the same concrete-to-abstract progression. A player who finishes the Fortnite chain has already built most of the intermediates needed for the others, and the second chain typically takes a third of the time of the first because the heavy lifting on the water, plant, and combat branches is already done.

The pattern also explains why some players get stuck on labels like War, Battle, or Duel. Those three results are shared between a surprising number of late-game chains, and the engine treats them as a small reusable cluster rather than a single branch. Treating them as a cluster, instead of as a linear sequence that belongs to one chain, makes it easier to plan new recipes later because the player already knows which parents are likely to produce the same combat vocabulary regardless of the cultural target on the right-hand side of the merge.

Reading the engine’s vocabulary as a player

After a few hours with the game, the engine’s labels start to feel less like random words and more like a small private dictionary. The author of the sandbox appears to have built the recipe table with a few guiding principles: doubles of the same element often escalate to a larger version, a natural element plus a kinetic element tends to produce an energetic version, and a tool element plus a raw material tends to produce a refined material. Most of the late-game results sit on top of these patterns, and the Fortnite chain uses each of them at least once. The single hardest pattern to read is the difference between an abstract result (War, Duel, Battle) and a concrete one (Sword, Wall, House), because the engine accepts similar-looking parents for both and only the result label tells the player which way the combination was resolved.

For players who want to plan their own chains without referring to a written list, the practical exercise is to look at any late-game result in the Discoveries panel, write down its visible label, and ask which of the four starting elements would have the weakest connection to that label. Whichever element is weakest is usually the one that the engine expects the player to add last, and that is the side of the chain where the player should start looking for parents. This trick is not a rule, but it works often enough to be a useful starting point when the player wants to build a custom chain toward a result that the published lists do not cover.

Frequently asked questions

What are the four starting elements in Infinite Craft?

Earth, Water, Fire, and Wind. The game gives the player these four elements at the start, and every other result is produced by combining them with each other or with elements the player has already discovered.

Is there a faster recipe for Fortnite than the one in this guide?

Some players have reported shorter chains that reach Fortnite in around 12 elements, but those chains depend on recipe table entries that have not been stable across all versions of the engine. The 28-element chain is the most reliable for a player on a fresh browser session and works on the live game at the time of writing.

Why does the same combination sometimes succeed and sometimes fail?

Two reasons. First, the engine may resolve the combination differently depending on the order in which the elements are dropped, even though the inputs are the same. Second, the engine can be inconsistent between browser sessions, especially after a refresh of the recipe table by the author. The chain in this guide avoids the order-sensitive combinations as much as possible, and the fallback list covers the most common stuck points.

Does Infinite Craft save progress between sessions?

Yes. The game stores the player’s discovered elements in the browser’s local storage, so the discoveries panel is preserved across refreshes and browser restarts on the same device. A different browser or a private window starts a fresh library.

Can the Fortnite result be combined with other elements to produce new results?

Yes. Fortnite is a valid parent like any other element, and combining it with other late-game results produces further named concepts. The exact list depends on the current recipe table, and the engine does not cap the number of discoveries.

Why does the engine reject a combination that looks correct?

The engine pairs elements by their internal name, not by what the label looks like. If the internal name of an element does not match the recipe, the engine rejects the pair even when the label seems to imply a sensible result. The fastest recovery is to recreate the missing parent from a known earlier step.

Is there a way to see the parents of a result in the Discoveries panel?

No. The panel shows the label and the date of discovery, but it does not show the parents. A player who wants to keep track of parents needs to write the chain down or screenshot the workspace as the chain progresses.

What happens if the player accidentally combines the wrong two elements?

The engine returns a new result if the pair has a recipe, and adds it to the Discoveries panel. If the pair has no recipe, the two elements bounce back and no result is created. The player can ignore the unwanted result, hide it from the panel, or keep it as a side branch. There is no penalty for failed attempts.

Can the chain be completed on a mobile browser?

Yes. The game is a single-page JavaScript application, and the touch interface works on a mobile browser. The Discoveries panel is narrower and requires more scrolling, so the search bar is even more important on mobile than on desktop.

What is the best way to learn the engine’s vocabulary?

Run short chains for common concepts (a city, a song, a famous person) and watch the labels the engine accepts. After a few hours, the engine’s vocabulary starts to feel predictable, and long chains like the Fortnite recipe become easier to plan without referring to a written list.

How to make Fortnite in Infinite Craft: the full recipe path