Algorithms

2-Look OLL Explained

By CuberPal Editorial Team · Updated 2026-08-26 · Editorial standards

Quick answer

2-look OLL orients the last layer in two algorithms or fewer. First use one of three algorithms for the unsolved edge patterns to make the top cross; then use one of seven corner algorithms to orient the remaining top stickers. The solved edge-cross state needs no first algorithm, which is why some resources count displayed states differently.

If you searched for 2-look OLL algorithms, the compact answer is 10: three algorithms for unsolved top-edge patterns and seven for corner orientation. You identify and solve the edges first, then identify and solve the corners. This covers every valid OLL state without learning the full 57-case set.

2-look OLL cheat sheet

  • First look: distinguish the line, L, and dot edge patterns; a completed top cross skips this algorithm.
  • Second look: distinguish Sune, Antisune, H, Pi, T, U, and L corner families.
  • Learn line and L first, then dot; learn Sune and Antisune before adding the remaining corner families in small groups.
  • Train recognition from several U-face angles separately from execution, then combine both in randomized cases.

What two-look OLL solves

OLL means Orientation of the Last Layer. At the start of OLL, F2L is complete but some last-layer stickers do not face upward. Two-look OLL first orients the four top edges to form a cross, then orients the four top corners. Piece positions do not need to be correct yet; PLL handles permutation afterward.

The two stages reduce a 57-case one-look system to a compact beginner set. The usual count is three edge algorithms plus seven corner algorithms. A solved edge-cross state needs no edge algorithm, so some resources describe the visible case count differently. The important promise is functional: from every valid OLL state, you can reach an oriented top in at most two algorithms.

First look: read the edge pattern

Ignore the corners and inspect only the four top-layer edge stickers. You will see a cross, a line, an L shape, or a dot. The cross means edge orientation is already complete. The line and L are orientation-sensitive: align them exactly as your algorithm reference shows before turning. The dot has no oriented top edges and generally requires an edge algorithm before reaching another edge pattern.

Use a consistent viewing rule. For example, hold the line horizontally and the L in the back-left, if that matches your chosen algorithms. Do not rely on vague visual memory; verify which two top edge stickers are oriented. An incorrect U adjustment is one of the most common causes of an algorithm that appears not to work even though the moves were executed correctly.

Second look: identify the corner family

Once the top cross exists, the seven corner patterns are commonly labeled Sune, Antisune, H, Pi, T, U, and L. Names vary slightly across teaching resources, so learn both the visual cue and the label used by your trainer. Count oriented top corners first, then inspect where the remaining top-color stickers appear on the sides.

Sune and Antisune are mirrors with one oriented corner. T and U can look similar from a rushed angle, while H and Pi differ in the side-sticker arrangement. Rotate only the U layer to match the case, not the entire cube. Build one reliable cue per case, such as oriented-corner count plus a side pair, rather than memorizing the whole sticker picture.

Choose algorithms for reliability and grip

Multiple algorithms can solve the same case. Start with versions that use familiar triggers, have a clear setup, and return your hands to a comfortable grip for PLL. A sequence that is one move shorter on paper can be slower if it causes a regrip or frequent lockup. Follow one trusted set until recognition is stable before comparing alternatives.

Learn the first and last move as part of the algorithm. If a case begins with a U adjustment, decide whether that adjustment belongs to recognition or to the algorithm and stay consistent. Practice from the actual grip left by F2L. An algorithm performed quickly from a prepared display grip may fail during solves if the entry position was never trained.

A sensible learning order

Begin with the line and L edge cases, then add dot. For corners, learn Sune and Antisune first because their finger patterns and mirrored shapes reinforce one another. Add one or two of H, Pi, T, U, and L at a time. Keep using your previous solution for unlearned cases until the new one can be recalled without guessing.

Use a three-step standard before calling a case learned: identify it correctly from four U-face angles, execute it slowly without a prompt, and recall it after at least a day away. Ten fast repetitions in one sitting measure short-term imitation. Spaced review and random presentation measure whether the case will be available inside a real solve.

Drill recognition separately from execution

For recognition practice, generate or set up a case, look for one second, name the family and required adjustment, then reveal the answer. Do not execute. This isolates visual classification. For execution practice, start from a known aligned case and repeat the algorithm at a controlled pace, watching for regrips and final hand position. Only then combine both in random drills.

Balance new and old cases while learning so similar shapes compete for attention. Later, use realistic random frequency to test solve readiness. Track three outcomes: correct identification, correct algorithm recall, and clean execution. If a rep fails, label the stage that failed. Repeating the moves does not fix a visual confusion, and studying diagrams does not fix a poor U2 fingertrick.

How to use two-look OLL in normal solves

Finish the fourth F2L pair while keeping the top face visible. As the pair enters, begin reading the edge pattern. Make the smallest U adjustment that aligns your case and execute the edge algorithm. During its final moves, look for the corner pattern rather than watching pieces you already know will orient. This creates a deliberate transition between the two looks.

Do not chase a seamless transition before accuracy. Pause, confirm, and execute cleanly until wrong algorithms are rare. Then shorten the confirmation pause. Time the complete OLL phase, but occasionally record recognition and execution separately. A two-look system with immediate recognition can outperform a partially learned full OLL set that causes uncertainty.

Common two-look OLL failures

If the top cross does not appear, check the initial orientation and U adjustment before blaming the algorithm. If the cross appears but F2L is damaged, a face turn was reversed or a layer was misaligned. If the corner algorithm produces another corner case, you may have started from the wrong angle. Reconstruct at one move per second and find the first state that differs from the reference.

Another failure is learning several algorithms with nearly identical starting moves in one session. Interference creates guesses. Limit new material and interleave it with well-known cases. Avoid recognizing by color arrangement on the front face alone; cube color schemes and U adjustments change the view. Recognition should be based on orientation relationships that remain true regardless of the specific side colors.

When to move from two-look to full OLL

Stay with two-look OLL until every case is automatic enough that the phase rarely breaks a solve. Full PLL is often learned first because it has 21 cases and removes a permutation look. Consider full OLL when F2L and PLL are stable, two-look recognition is fast, and you can maintain a few new cases per week without losing old ones.

Upgrade by family rather than by case number. Learn shapes that are easy to distinguish or that replace a slow two-look combination. Keep the two-look route as a safe fallback while a new case is uncertain. Your next practice session should make the four edge patterns and seven corner families boringly reliable; that foundation makes every later OLL case easier to classify.

Continue the learning path

CFOP algorithms

Learn a small set, drill recognition, then use spaced repetition to retain it.

Open this topic cluster →

Turn this into practice

CuberPal combines a WCA-style timer, AI solve analysis, CFOP lessons, algorithm catalogues, spaced repetition, and a camera cube solver so speedcubing advice becomes a daily training loop.

Download CuberPal
CuberPal OLL Catalog displaying an OLL case, cube diagram, move sequence, and playback controls

Frequently asked questions

How many algorithms are in two-look OLL?

A common system uses 10 algorithms: three for unsolved edge patterns and seven for corner orientation. The already-solved edge cross needs no algorithm, so some resources count displayed states differently.

Is two-look OLL enough for sub-20?

It can be. F2L efficiency, Cross planning, PLL, recognition, and execution all affect the average. Full OLL saves a look but is not a prerequisite for every sub-20 solver.

Should I learn full PLL before full OLL?

That is a common progression because full PLL has 21 cases versus 57 OLL cases and removes one full permutation look. Choose based on your measured bottleneck and available study time.

Why does my OLL algorithm keep breaking F2L?

Usually the case was held at the wrong U angle, a prime turn was reversed, or a layer was misaligned. Replay slowly from the required orientation and compare the cube after each short trigger.

Sources and fact checks

Keep improving