What to use instead of Canva or PowerPoint for writing crochet and knitting patterns

By Ali Lehrman · September 9, 2026 · Updated October 1, 2026

Canva and PowerPoint will both get you a PDF at the end. Neither of them knows what a pattern is. They will not number your rounds, they will not number your photos, and they will not tell you a round does not add up. NodeStitch is a browser based layout tool built for writing crochet and knitting patterns. It numbers rows and rounds as you type, renumbers photos when you insert one, and flags stitch counts that look wrong.

Those programs are not bad. They are just not built for this.

I wrote patterns in PowerPoint for years, and then moved over to Canva when PowerPoint got too tedious to keep doing. I want to be fair to both, because each one made sense at the time.

PowerPoint is better than people give it credit for. It gives you a fixed page and you can put anything anywhere on it, which is exactly what a pattern page needs. That is why I wrote in it for years, and it is still where I would tell someone to start before a word processor.

Canva makes a good looking cover. That is real. My covers got better the day I started using it. And there is a boatload of art sitting behind it: photos, icons, banners, backgrounds, things you can generate on the spot. If you like putting cute images in your patterns, that is a real reason to stay in Canva, and I want to be straight about it, because I have none of that. My app gives you no image library at all. You can still use those images, you just have to go and get them: download the icon from wherever you found it, or export the graphic out of Canva, save it, and upload it like any other photo. That is an extra errand every time, not a wall.

Two others deserve a mention. Excel is the best thing anywhere at one specific job, a stitch count column you can check with a formula. And Word will hold a pattern that is text and a stitch key and nothing else, though the moment you add photos you will wish you had started somewhere with a real page.

The problem is that a pattern needs all of those things in one file, and every one of those programs is missing most of them. So you write in one, lay out in another, and do the checking in your head.

Writing it twice

I wrote my patterns in a notebook first. Sitting there with the hook in my hand, writing down what I actually did as I did it, because that is the only way the pattern ends up matching the thing.

Then I typed the whole notebook into PowerPoint.

That is the part nobody warns you about. Not the designing. The retyping. Every round, by hand, out of your own handwriting, into a program that does not help you in any way while you do it. And it is not just typing, because you are making layout decisions at the same time, so the transcription takes three times as long as transcription should.

The errors get in here too. You skip a line. You type “Rnd 14” twice. Your notebook says one thing and the file says another and the file is what ships.

That part is gone for me now, and it is the thing I did not expect to care about most.

You photograph your notebook page and it comes back as a pattern rather than a block of text. Every round is a numbered line with the number as an actual number, stitch counts in parentheses come back as counts, “Rnds 4 to 6” is recognized as a span worth three rounds, and a line reading “Note: change to brown yarn” is marked as a note instead of eating a round number.

You can upload more than one photo at a time, so it is not one page at a time. Photograph the whole pattern out of your notebook and send all of it at once, and each page comes back as its own page. You pick whether it lands as a written pattern, a plain table or a bubble table.

It is reading my handwriting. It is not inventing rounds I did not work.

Labeling every single line

Here is the one thing that really made me want to pull my hair out, and it sounds small.

Every line of a pattern is a new round. So every line needs a label. Rnd 1. Rnd 2. Rnd 3. All the way down. You type it, every time, on every line, in every pattern you have ever written.

And then you insert a round in the middle and every label under it is wrong.

No program I used had any idea that the lines of a pattern are a numbered sequence. Canva has text boxes. PowerPoint has text boxes. A text box does not count. And a numbered list, if you go looking for one, does not know that some of your lines are notes and some are rounds and the notes should not eat a number.

So you sit there typing “Rnd 27” like a person doing data entry, on the creative project you started because you wanted to make something.

This is the part of my own app I use hardest, so weigh it accordingly. A text box in Pattern mode numbers the lines as you type, with the prefix set to Rnd, Round, Row, R, None, or anything you type yourself. Notes and bullets get no number, so a note between two rounds does not eat a round number. And if the numbering is wrong you retype one label as “Row 10:” and it works backward from that to renumber the whole box, prefix included, instead of you scrolling down and retyping forty labels.

Multi round spans

Every designer writes these. Rnds 4 to 6, same instruction, three rounds, one line.

In Canva or PowerPoint you type the range yourself and you type the count yourself, and nothing anywhere knows that line is worth three rounds. So the next round’s number is up to you to get right, and if the count breaks somewhere inside the span, it breaks silently.

In NodeStitch the span is a number on the line, not something you typed into the text. It renders as Rnd 4 - Rnd 6: with [3 Rnds] after it, the following line starts at 7 on its own, and when the stitch math runs it expands that span into three separate rounds and checks each one. A span that quietly stops adding up on the middle round is not invisible.

The count beside the line is yours to style. Square brackets, parentheses or no brackets at all, and you can turn it off entirely if you would rather the range spoke for itself. Because the span is a value rather than typed text, changing your mind about that does not mean editing forty lines.

The photo numbering thing

Same shape of problem, more expensive.

You shoot the photos in order. You lay them out in order. Then you realize step 7 needs a photo, because a tester is going to get lost there without one.

So you insert it. And now every photo after it is wrong. Photo 8 is photo 9. The caption under it is wrong. The line in the written pattern that says “see photo 12” is wrong. The file sitting in your folder called IMG_4471_step12 is wrong.

You have to find every one of them, because the one you miss is the one a tester emails you about.

The worst one was a pattern with over 100 photos in it. I inserted one image in the middle and spent at least half an hour renumbering the rest.

There is no version of Canva or PowerPoint where that renumbering is not manual. It is not a missing feature. Those programs have no concept of a photo having a number in a sequence, so there is nothing there to update.

Mine does. Photos are labeled by their order on the page, so inserting one at step 7 relabels everything after it, and you can unlink any single photo you want to name by hand. And a “see photo 12” in your text that is linked to its photo changes with it, in the same step. A reference that is not linked yet stays as you wrote it, and Pattern Review tells you about it, which is the next part.

What I check before a tester sees it

None of this needs my app. If you are staying in Canva or PowerPoint, this is the list I would run, and it catches most of what testers find:

1. Every round total against the increases and decreases you actually wrote on that line. Not the total you meant. The one your own text produces.
2. Repeat brackets. Multiply the count inside the bracket by the repeat number and check it against the round total.
3. Round and row labels, in order, with no number used twice and none skipped. This is the one that breaks after you insert something.
4. Photo numbers against every place in the text that references a photo number.
5. Every abbreviation used in the body against your own stitch key. Both directions. Keys go stale.
6. Round versus row, used consistently. If you work in the round and turn for the last two, say so where it changes.
7. The exported PDF, opened on a phone. That is where a lot of people read patterns and it is where a nine point stitch count column disappears.

Number 1 is the one that gets skipped, because it is tedious and because you already know what the total is supposed to be. That is exactly why it is the one that ships wrong.

For what it is worth, the app does the first five of these for me now. Five happens once I have marked which text box is my stitch key, and then it reads the key against the pattern both ways without being asked again. Six and seven are still mine, and seven is the one I would not skip no matter what you write in.

The comparison

If your patterns are short and text only, none of this matters much. Write it in whatever you already have open. And if charts are what you need, the charting programs are compared here.

What Pattern Review actually looks for

The numbering is the boring half. The half I did not expect to need is the checking.

Pattern Review reads what you wrote and reports what looks wrong. Some of what it catches:

• A round that needs more stitches than the round before it produced. You wrote a repeat six times when the previous round only made enough for three.
• A repeat that does not divide evenly into the stitches available.
• Stitches left unworked at the end of a round, when the instructions account for fewer than you have.
• A fasten off, followed by a section that keeps going without ever rejoining.
• Assembly instructions that say to join two pieces stitch for stitch when the two final counts do not match.
• The same stitch written two ways, “sc” on four lines and “SC” on the fifth, but only when both forms genuinely appear in your pattern.
• A gap in your photo numbering, and a photo that exists and is never referenced anywhere in the text.

Several of those are things a tech editor charges money to find, and I want to be clear that this does not replace one. A tech editor reads for the things a machine cannot see. But there is no reason a person should be paid to notice that I fastened off and kept crocheting.

It does not write patterns. It helps a designer write their own. That distinction matters to me and it should matter to you. It flags. It does not fix, it does not correct, and it does not generate a single stitch. If it thinks round 14 is wrong, it tells you round 14 looks wrong and you go read round 14. You are still the designer. I would not use it otherwise and I would not have built it otherwise.

Fiber communities are suspicious of anything with AI attached to it and they are right to be. AI generated patterns waste people’s yarn. Snappy Tots keeps a directory of 88 real designers specifically so people can tell the difference. So I say the line first instead of waiting to be asked.

The honest catch: a free account lets you build the pattern but cannot export the PDF, and reading a pattern in from a photo is on the paid plan too. I would rather tell you both of those here than have you find out at the end of a pattern.

If you are not switching

Fair. Here is what I would do inside Canva or PowerPoint to make these hurt less.

Put the round labels in their own column or their own text box, separate from the pattern text. It does not stop you typing them, but it means renumbering is editing a short list rather than editing inside sentences.

Do not put photo numbers in caption text either. Put the number in a small separate text box on top of the photo, so renumbering is a one character edit. Rename the photo files to match at the same moment, never later.

Build the stitch count column in Excel where a formula can check it, then bring it into your layout as an image. You lose the ability to fix a typo without going back to Excel, and you gain a column that is actually correct.

And write the stitch key last, from the finished pattern text, not first from memory. A key written first is a key that is missing whatever you added on round 30.