Lace charts vs. written instructions: Should knitting patterns include both?
Charts are common in knitting patterns that include lace, cables, or other intricate stitch patterns. While some knitters swear by them, other prefer following written instructions.
In this blog post, I’m going to talk about the benefits of each, and hopefully convince you to include both in your knitting patterns if you’ve got a complex stitch pattern to convey.
As an example of a chart and its corresponding written instructions, below are both a charted and written out version of the same stitch pattern (Cat’s Paw Eyelets from So Woolly).
Charted version of Cat’s Paw Eyelets
Written row instructions for Cat’s Paw Eyelets
Why patterns include charts
As you can see in the image above, charts provide a visual representation of a stitch pattern by representing different stitches with common symbols.
They’re super useful when knitting lace patterns because as you’re knitting you can see what the pattern is supposed to look like and which stitches are supposed to stack on top of each other, allowing you to easily confirm you’re knitting correctly.
Some knitters prefer working from charts because they can see which stitches need to be knit and where, rather than having to read out sometimes lengthy written instructions.
Why patterns include written instructions
Written instructions list out how to knit the row stitch by stitch, as shown in the second image above.
Sometimes newer knitters prefer to knit from the written instructions, because it clearly spells out what you’re doing and you don’t have to worry about what all the symbols mean. Some experienced knitters prefer working from written instructions as well.
Having written instructions is also important for accessibility because screen readers can’t read charts, or low-vision knitters might find that the chart symbols are too small to follow.
For me personally, though I typically prefer working from a chart, I do use an app for tracking row count and there’s an area to paste written instructions below the counter, so I often end up using the written instructions so I don’t have to keep switching between the pattern and row counter.
Should you include both?
I recommend including both in your pattern for complex stitch patterns, because knitters tend to prefer one over the other, so giving them the option to choose can provide a better user experience.
One exception to this is colorwork, which typically is only charted and no written instructions are provided.
Also, if you’ve got a very basic stitch pattern with only a few stitches repeated over a few rows, such as seed stitch, you may not need a chart.
Best practices for charts
Always include a key that indicates what stitch each symbol is.
If using a program like Stitchmastery, remove unnecessary RS/WS instructions from the key.
Stitchmastery will automatically put both the RS/WS instructions for a symbol in your key (ex. RS: k2tog, WS: p2tog), but often you’re only working increase/decrease stitches on the RS, so those unused WS instructions should be deleted.
Put repeats into a red border
For colorwork charts, ensure your chosen colors work in greyscale because not everyone has a color printer. Similarly, ensure colorwork charts are colorblind friendly.
Best practices for written instructions
Add repeats where they make sense.
Break up long sections of the same stitch.
For instance, if you’re using the Stitchmastery written output, you’ll need to clean it up because it will tell the knitter to k25 if that’s what’s in the chart. What knitter wants to sit there and count that high? Break it up by placing markers and instructions to “k to marker.”
Include stitch counts at the end of each row if there’s an increase or decrease in the total.
Ready to take your knitting patterns to the next level?
As a knitting tech editor, I can work with you to ensure your patterns are clear, accurate, and easy to follow. Visit my Tech Editing Services page to learn more and get started today! I also made the chart in this blog post, and can create charts for you as well.
