Five Nights TD 2 evolution turns a qualifying unit and current recipe materials into another form. Public guides describe a Unit Workshop, materials, Souls, mode-specific sources, and inherited enchantments, but exact recipes and inheritance can change. The live recipe and final confirmation must decide the action.
Choose one target, pin its current recipe, verify every source, and protect the input unit. Do not farm from an old screenshot or consume a rare copy until the output and inheritance fields are clear.
Record the complete recipe
Open the evolution or workshop interface and select the exact base unit. Match name, ordinary or Shiny state, skin or form, level, enchantment, and any locked marker. Write every required material, quantity, currency cost, unit level, account requirement, and prerequisite.
Open the output preview. Check the exact evolved name, rarity, attack type, element, placement cost, upgrade path, passive changes, tradeability, and whether the action is reversible. If any important field is hidden, delay the craft until a current source or direct test answers it.
Take a screenshot with the date. Weekly updates can alter quantities or sources. Reopen the recipe before the final craft even if farming took only one session.
Find materials from the current client
Use the material’s own detail or source button first. Follow the listed Game, Night, difficulty, mode, event, Merchant, quest, shop, Present, or crafting route. Community sources mention batteries, springs, ashes, clocks, event items, and other materials, but not every material belongs to every recipe.
Run the source once and verify the reward screen and inventory change. Record amount, completion time, difficulty, active bonus, party size, and failure risk. Repeat enough times to estimate your own route; do not promise a fixed drop or hourly yield from one run.
If the material is event-bound, read the end timer and remaining attempts. Confirm whether leftover currency or ingredients survive. Do not begin a long recipe when the remaining event window cannot realistically support it.
Protect the input unit
Lock the base unit when possible and remove it from trade or feed selections. Check whether the team still needs that copy for Story, Endless, Boss Raids, Challenges, or a Hero quest. If evolution consumes the only reliable carry, make sure the output can immediately replace its role.
Keep duplicates required by the recipe separate from duplicates reserved for collection or trade. Do not rely on portrait alone when variants share art. Read full names and markers before selecting inputs.
For a Shiny base, do not assume the output stays Shiny. For an enchanted or leveled base, do not assume those fields transfer. A community guide reports inheritance behavior, but the current confirmation and resulting card are the only safe proof for your copy.
Decide which unit to evolve first
Start with the account’s current failure. If early Story leaks, an expensive evolved carry may not solve the opener. If bosses survive, compare the output’s focused damage. If long runs lack control or economy, a damage evolution may have lower impact than another system upgrade.
Calculate the full cost: materials, currency, base unit, duplicates, event time, and resources that cannot be spent elsewhere. Compare that cost with leveling the current carry, acquiring support, or building a cheaper unit. Evolution is valuable when the output creates a tested improvement, not merely a rarer card.
Use the tier hub to define the role and the Units Dex to find alternatives. Avoid evolving several units halfway; finish one route that enters the active team.
Complete the evolution safely
Return to the recipe on a fresh current server. Match every input and output again. Remove any accidental valuable selection. Read the warning, cost, and resulting form. Take a before screenshot, confirm once, then wait for the inventory to update.
Open the result and compare level, enchantment, Shiny marker, tradeability, stats, passive, and upgrades with the preview. Lock the new unit. If anything differs, do not repeat the process; capture evidence and use creator-owned support.
Test the evolved form on a familiar stage before spending more. Learn new attack shapes, forms, or active abilities. A different placement or upgrade order may be necessary.
Troubleshoot missing recipes or progress
Confirm that the selected unit is the correct form and meets the visible level or account requirement. Clear filters and check whether the recipe moved to another workshop tab after an update. Verify material names and quantities; similar icons can represent different items.
If a source does not drop the material, reread mode, difficulty, Night, event status, and reward pool. One failed drop does not prove the source is wrong if chance is involved, but a source label that changed should override an old guide.
If a quest or recipe counter does not advance, test one qualifying action, rejoin once, and stop spending if it remains stuck. Keep screenshots and report the current build and exact step.
Current confidence
Evolution, workshop-style crafting, material farming, and evolving unit forms are community corroborated. Exact recipes, quantities, level gates, Souls cost, material sources, drops, output stats, enchantment inheritance, Shiny inheritance, tradeability, and reversibility need the current client. This guide was checked September 1, 2026.
Use the farming guide to measure material routes and enchantments before rerolling the finished form.