Why run-length encoding saves space
Counts each run of one colour instead of listing every pixel. It saves space on long runs, like an all-white row, but saves little when colours change every pixel, like a checkerboard.
Understanding Why run-length encoding saves space in ACARA Digital Technologies Years 5–6
What it does: Counting the numbers in each code shows which one uses less space. The code with fewer numbers is more efficient. A single long run is stored as one count and one colour, so 10 pixels need only 2 values. Long runs of one colour give short codes. The all-white row is just one run of 10. When the colours change every pixel, each run has a count of 1, so you still write as many counts as there are pixels.
Common mistakes: The code 8W says there are 8 white pixels, but the row has only 7 W's. The row should be "WWWWWWWW" so the 2-character code can be compared with an 8-pixel row. A checkerboard row changes colour every pixel, so the run-length code (16 characters) is longer than the row (8). The test should use > to show the code is longer.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 59–71) and word search (Modules 44–71).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
run-length encodingFill in the Blanks
Spot the Error
Student with a class code? Join your class →