The internet is billions of devices communicating with each other.
Which sounds impressive.
Until you realise communication only works when everyone agrees how to communicate.
Imagine sending:
“HELLO.”
and receiving:
“¿H€@#?”
Excellent. Very productive.
That's where network protocols come in.
A protocol is simply a set of agreed rules for communication between devices.
Basically:
The internet has rules because apparently “everyone just do whatever” wasn't a viable networking strategy.
Protocols are basically the internet's handshake
Think about meeting someone.
You offer a handshake.
They offer a fist bump.
You panic and switch to a wave.
They've already gone for the high five.
You both consider moving countries.
The problem?
You didn't agree on the rules.
Devices have the same problem.
When computers communicate, they need agreed rules covering things like how data is sent, received and interpreted.
Those agreed rules are protocols.
Different protocols have different jobs
Here's where students often get buried underneath acronyms.
HTTP.
HTTPS.
FTP.
SMTP.
IMAP.
It starts looking less like Computer Science and more like someone fell asleep on their keyboard.
But you don't need to treat them as one giant collection of random letters.
Think of them as staff members.
Everyone has a job. 
And then email needed its own staff
Email doesn't simply teleport from your keyboard into somebody else's inbox.
Different protocols help handle different parts of the process.
Two important ones are:
SMTP and IMAP.
And they're much easier to remember when you stop treating them like random acronyms.
SMTP — Simple Mail Transfer Protocol
SMTP is used for sending email.
That's the important bit.
SMTP → SEND
Imagine SMTP grabbing your email and marching out of the building with it.
“I send it. That's my entire personality.”
IMAP — Internet Message Access Protocol
IMAP allows you to access and synchronise email stored on a mail server.
This is why you can check your email on your phone and then open your laptop and see the same mailbox.
IMAP → ACCESS + SYNC
Your messages remain managed on the server and changes can be synchronised across devices.
Very organised.
Slightly smug.
The ridiculously short version
If the acronyms start merging into one enormous networking soup, remember:
HTTP → web pages
HTTPS → secure web
FTP → files
SMTP → sends email
IMAP → accesses/syncs email
That's already considerably less terrifying.
Why do we actually need protocols?
Because networks contain devices made by different manufacturers, running different software, doing different jobs.
They still need to communicate successfully.
Protocols give them agreed rules.
Without those rules, one device could send data in a way another device doesn't understand.
Which brings us back to:
“HELLO.”
“¿H€@#?”
Not ideal.
The 20-second protocol test
Before you leave, see if you can answer these without scrolling back up.
What is a protocol?
A set of agreed rules for communication.
Which protocol is associated with web pages?
HTTP.
Which provides secure web communication?
HTTPS.
Which one transfers files?
FTP.
Which one sends email?
SMTP.
Which one lets you access and synchronise email?
IMAP.
Got those?
You're done.
The alphabet soup has been defeated.
Want a visual reminder?
If remembering HTTP, HTTPS, FTP, SMTP and the rest feels like someone handed you a bowl of alphabet cereal and called it revision, Lavenderbyte has a visual version.
The Network Internet Protocols Acronym Posters turn common networking protocols into simple classroom references.
And they're FREE.
[Download the FREE Network Protocol Posters on TES →]
For broader networking revision, you can also explore Lavenderbyte's Computer Networks Poster, covering key Computer Science networking concepts in one visual resource.
[View the Computer Networks Poster →]
Protocols aren't complicated because they're protocols.
There are just a lot of acronyms.
Once everybody has a job, they make considerably more sense.