BOX align is a minimalist match-style puzzle game where every move needs to matter. You clear boxes by combining three or more of the same color, but later levels add fixed boxes, cages, bombs, chameleons, hidden boxes, and wild-card style pieces that punish casual movement.
This guide focuses on strategy and box behavior. It is not a level-by-level solution guide.
Where to play: itch.io hosts a free demo of BOX align. The full 99-level game covered here is on Steam and Nintendo Switch.
Essential Tips
1. Plan From the Final Clear Backward
The goal is clearing every box, not making the nearest match.
Before moving, identify which colors or locked pieces are hardest to clear. Build your first moves around those constraints.
2. Remember That Every Move Must Match
You cannot freely shuffle the board.
Because moves must create a match, you need to think about setup before touching a box. If a move clears something but strands another color, it may be wrong.
3. Prioritize Caged and Fixed Problems
Locked pieces narrow your solution space.
Can’t Move boxes and Cage boxes should shape the whole plan. Treat them as anchors and solve flexible boxes around them.
4. Use Special Boxes as Last-Resort Flexibility
Wild-card behavior is strongest when the board is constrained.
Do not spend Special boxes just to make an easy early match. Save them for colors that would otherwise be difficult to group.
5. Put Bombs in the Right Position
Bomb boxes activate only when positioned correctly in a combination.
Bomb boxes need to be in the middle of a combination to eliminate surrounding boxes. Plan their placement before triggering them.
6. Account for Chameleon Timing
Changing colors can solve or ruin a plan.
If a Chameleon is near a solution, wait for the useful color only when doing so does not break the rest of the board.
7. Reveal Unknown Boxes Safely
Unknown boxes add uncertainty to late-level puzzles.
Clear around hidden pieces early enough that you still have options after they reveal.
8. Accept Restarts as Part of Learning
There is no undo system in the researched build.
If a chain goes wrong, restart with a better plan instead of forcing a broken board.
Puzzle Tips
- Mark the blockers first: Fixed, caged, and hidden pieces determine the real route.
- Avoid isolated colors: Do not clear two boxes if the third copy gets stranded.
- Save flexible pieces: Special boxes are strongest near the end.
- Use bombs deliberately: A poorly placed bomb can clear needed material.
- Take screenshots for hard levels: Visual review helps when there is no undo.
Resource Management
- Moves: Each move must advance the total clear, not just reduce clutter.
- Space: Avoid creating isolated pockets that cannot form triples.
- Special boxes: Spend them on bottlenecks, not convenience.
- Patience: No time pressure means planning is the main resource.
Hidden Mechanics
| Mechanic | What It Does | How to Use |
|---|---|---|
| Mandatory matching | Every move must result in a match | Plan before dragging |
| Can’t Move boxes | Stay fixed in place | Build matches around them |
| Cage boxes | Locked until matched with same-color sequence | Free them early |
| Bomb boxes | Clear surrounding boxes when centered in a combination | Position before triggering |
| Chameleon boxes | Change color over time | Wait only when it improves the plan |
| Unknown boxes | Reveal after a combination | Reveal while options remain |
Common Mistakes to Avoid
- Do not clear easy matches first by default - Solve the bottleneck.
- Avoid spending Special boxes early - You may need them later.
- Do not trigger bombs casually - They can remove useful boxes.
- Avoid ignoring color readability - If colors are hard to distinguish, slow down and use position as a second cue.
- Do not copy exact level solutions without visual support - Puzzle layouts are easier to follow when you can see the board state.
Summary
| Category | Top Tip |
|---|---|
| Planning | Solve locked and fixed boxes first |
| Special Boxes | Save flexible pieces for bottlenecks |
| Bombs | Center them intentionally |
| Hard Levels | Restart with notes instead of forcing bad states |
Did this answer your question?
Your feedback helps keep the useful answers visible.Next answers
Community notes0
No community notes yet.
Sign in to contribute