Base64 Encoding

[@IreshDissanayakaM]

This is THE explanation of BASE64. Thank you!

[@nandharamya9612]

what the fuck?????????????????he literally explained everything about base64 encoding under 4 minutes.hatsoff sir...

[@lionbrunch4244]

Huge thanks, super concise and at the same time more enjoyable and understandable than I could imagine!

[@user-ek9ez7ho6f]

this is best explanation ever! just insane!

[@ant-dev]

i love this. now i got a better idea of how im handling RSA keys for e2e encryption on my webapp. thank you for your knowledge 😊

[@kennethcox6895]

2:36 was actually horrifying. like horror comedy.

[@oliverodgers2012]

best way to explain how it works, really good video, thank you so much

[@Dfeneck]

Of all the damn characters to chose from. They picked FORWARD SLASH. Smh.

[@khalief_.]

Fr

[@MarcoAntonio-jq7lo]

That's why base 64 url encoding exists

[@schenken660]

Hey, thanks to everybody that likes the video, I appreciate it. But don't expect another one (God knows how I managed to make this one!) I'm actually just totally pissed offf with programming. I'm fecking hopeless at what I do could not code myself out of a wet paper bag!

[@lineup1837]

Don't give up Get some help a tutor

[@UxJ7]

Thanks for the simple yet highly effective explanation.

[@AliRachid]

Thank you very much, a crystal clear explanation.

[@kutry]

Everybody gangsta till you find out there is no 64

[@theendofthischannel6421]

Everyone gangsta till you realise there is a 0

[@MrAitSous]

You're the best! Thank you for the explanation.

[@lisogie]

This was SO helpful and made so much sense! Thank you so much

[@kitkatcats3360]

Great video

[@liamvanderviven1423]

Very nice to listen to and you explained it very well, thanks!

[@poojaheera7658]

Thanks for the easy explanation.👍

[@dannnyxz1511]

Thanks man, such an awesome explanation!

[@angel-sx5vt]

who here is from nullxiety-

[@yazminsoto2937]

Every reply

[@morningboy_]

Yep

[@BARBET1062]

Nah i just want general knowledge

[@candice.sanders2136]

yes

[@Hiwww_s]

Yes

[@nirajthegreat5742]

awesome explanation keep going good work

[@timosos7]

Wow this really helped a lot thank you You should deserve more subs Make more great educational content! :D

[@babylonfive]

good stuff. no one ever addresses the more 'embedded processing' or graphics raw-binary data view when describing BASE64. You can I think just start with a 24 bits of raw data (ADC result, or a set of 24 boolean sensor values) and code them into the 4 bytes. It's not clear to me how they would be unpacked at the far end. Just noticed how old this vid is, but nice nonetheless.

[@salah2ali25]

very good explain

[@rogerredhat1431]

I agree with the other comments, perfectly explained. A well made video too with good humour. Thanks!

[@Baskemtball]

literally all i wanted to know when i looked up base64 encoding keep up the great work :)

[@marisaeggs]

This is an amazing explanation, thank you

[@parsalotfy]

This video is better than the other which was speaking so fast and I couldn't understand any thing and the animation of Your video is very better, Thank you very much

[@danielwinkler1910]

fantastic explanation. cheers!

[@kk.engineer]

Great job mate, very helpful, thanks !

[@fahrulrputra2589]

This is the best explanation you will ever get out there.

[@sircosm]

Its nice to see that you make Ableton Live videos as well

[@schenken660]

Yes, hehe! Ex-computer programmer turned music producer :-D

[@MarcoAntonio-jq7lo]

Great video bro

[@gedtoon6451]

The whole point of base64 is to be able to send non-printable byte data over a channel that only supports printable data. It makes no sense to show an ascii string being converted to base64. You could just send the ascii string! I think some people think that base64 is some kind of cryptography tool: it is not.

[@schenken660]

You don't really know what you are talking about, do you?

[@gedtoon6451]

@@schenken660 Google the use cases for base64.

[@user-4wijmkbkfi]

Great explanation! Thank you very much😘

[@forg9648]

Thank you! This is really helpful!

[@vkhemant]

Awesome awesome 👏👏👏

[@leocris1100]

excellent explanation!

[@rajeshseptember09]

This is outstanding. Make more videos!

[@emekaanachebe415]

excellent! Thanks for this.

[@jitenanand3494]

Very good Animation for teaching

[@Luke-c8q1k]

Hi - how do you work out Base64 coded string back into it's original state? The video explains how and goes to QW5K but if we was given QW5K how do we revert this back to and without knowing it was originally and?

[@tymothylim6550]

Thank you very much for this video! It was very clear and educational :)

[@dipeshvishwkarma8158]

NICE

[@swagmuffin9000]

it made a lot of sense, except i wasn't fully understanding the "=" part.

[@Prince-wv8nm]

superb

[@VenuGopal-vj1cm]

Super vide

[@nexisia]

definitely not learning this just for a Roblox game

[@user-wt5vo3xh7d]

lol

[@kadenvanciel9335]

The chosen base64 encoding peeves me because it's very confusing, compared to the type of system KZbin uses according to Tom Scott. I prefer it being like all other number systems that use Hindu-Arabic numerals and the Latin alphabet: the numbers 0-9 first, then the uppercase letters, then the lowercase, then the two extra symbols. I prefer KZbin's base64 system over the one described in this video. If KZbin really has been using Tom Scott's described system.

[@antwanwimberly1729]

Nice chart. We need that mapping asap

[@WilliamsLovesToLearn]

This was really good. Thanks

[@davidlira8853]

awesome animations

[@quiros7176]

Hi Im here because of Nullxiety :)

[@a_Playerwastaken]

me too

[@AbhishekYadav-mv9nk]

great explanation point to point.

[@renanaoki714]

Thanks!!! Long life to base64!

[@vforvendetta3527]

Simplest explanation. Nice

[@sergiobost7434]

Simply great.

[@danielvega646]

brilliant!

[@dawidolszewski6244]

amazing video. Thanks

[@OMARYassin1]

❤️❤️

[@raffiutama3580]

Good video, thank you

[@yltfy]

Very beautiful explanation.

[@justinturman]

Great video!

[@MiguelBeneditApa]

thanks a lot you deserve more subscribers

[@tsaibro]

ty! great job

[@louvflabianfelicilda1070]

This really help Thank you!

[@GeDaCrRe]

You don’t now how long it took me to realize.

[@TricoliciSerghei]

Great videoooo!! Sank you ;)

[@raghavendrac4710]

Thank you!

[@schenken660]

You're welcome 🙂

[@andreiinthedesktopworld1178]

Who is here from the guides: Section 3 because couldn’t find a walkthrough for section 3

[@vishnutcr6439]

How encode numbers and special character on ascii

[@DarkLevis]

Superb!

[@kirubagaran3749]

you teach better than ME graduates

[@chriszhu589]

really good video!

[@user-ox6ok4ud8f]

Thanks!

[@Noah-357]

In example g character, why did you padded out with two equal signs instead of one like the subsequent example ? Is it because you used base 4 so 4^0 > 4^1 > 4^2 > 4^3 = 64 ?

[@schenken660]

Simply because we need to pad it out to 4 characters. The basic process takes 3 bytes and turns them into 4 alphanumeric (text) characters. When you reach the end of the input, if there's less than 3 bytes, you still need to pad out it out to 4 characters. If 1 byte is left, that converts to 2 chars, so two pad chars (equals sign) are needed. If 2 bytes are left, that converts to 3 chars, so only one pad is needed.

[@SK-ju8si]

@@schenken660 why didn't u include this in the video? now it makes sense .

[@singhanveshak]

very clear

[@robot67799]

2:35 LOL

[@khors3075]

Thanks a lot, good man!

[@sebon11]

Am i dumb? Or why i still don't understand WHY do we need that instead of just sending data in the original encoding? (Without converting 3 into 4)

[@schenken660]

Because the original data might contain control characters which the receiving end would act upon. Base64 converts ALL data to pure text, (ie. letters and numbers - no control data) so the receiving end will see it as text only. Once all the data is received it will be converted back to its original format.

[@IStoleAllYourCookies]

Very useful

[@Outatime]

I don't understand the part with =... What if I have a whole word? Like Siema for example, the decode is U2llbWE= but why the =?

[@rustycherkas8229]

Because 'padding' like this is defined in the standard (the convention followed by all who choose to participate).

[@Outatime]

@@rustycherkas8229 yeah but.. why. i dont need a „because yes” explanation.

[@rustycherkas8229]

@@Outatime Why do shops usually display prices as "$1.50" instead of "$1.5"? Why put the 'useless' padding zero on the end??? Because that is the convention used in many cultures (although I've noticed this convention is 'loosening up' more and more.) Why? Because that is the way it is done. You're free to break with convention and NOT apply padding... Just know that files that don't follow convention are considered 'corrupted'... Why do we use '@' in email addresses? Because that is the accepted convention and LOTS of software has been written to both 'use' and 'expect' that convention to be followed... Why use 'A-Za-z0-9+/'? Why not 'a-z0-9A-Z!-'?? ("be unconventional") Why Morse code for 'E' just 'dot'??? The answer is "Because it is". Base64 encoded files will ALWAYS have a size that is evenly divisible by 4. That's the definition... Accept it.

[@Outatime]

@@rustycherkas8229 you’re missing my point. the equal mark would make sense if it was always there and if there was a rule to it, but no, sometimes it’s there, sometimes it isn’t. What I want to know is what that depends on.

[@rustycherkas8229]

@@Outatime Input is 'chunked' into blocks of 3 bytes... In 3 bytes - Out 4 chars + (nothing) In 2 bytes - Out 3 chars + "=" In 1 byte - Out 2 chars + "==" Output byte count is ALWAYS evenly divisible by 4... THAT is the definition. That is the rule you are trying to see. That is why an encoded file ends with 0, 1 or 2 "equals" ensuring the encoded file size is evenly divisible by 4... *Edit* Input of 4 bytes is input of 3 + input of 1. Input of 5 bytes is input of 3 + input of 2. Input of 6 bytes is input of 3... twice... I hope you can see the pattern forming...

[@philbutthead]

If I have to encode Hello There, do I have to do it every 3 letters? Please help

[@wowDepressive]

thanks much!

[@morningboy_]

Thanks!!

[@iJuce]

2:35 what was that 😂😂

[@yes-cj9em]

TYSM

[@sadBytes]

well that helped a lot, thanks!

[@saifhassan8764]

I tried encoding a number of 5 digits and it didn’t work so I encoded it using a encoding website and then copied the result and tried decoding it and it still didn’t work

[@vanessamontes231]

There is this KZbin channel called deeper making videos that give me the creeps, found this to help me decode some possible secrets

[@zeidennouri7817]

u are the best

[@schenken660]

hehe thx

[@user-kx2zv7tg3u]

Thx

[@user-yc9dp7nw4u]

0:02 Meow

[@RohitKumar-ev5ot]

Thanks a lot

[@naruomi7955]

Yo good content

[@vishnuvenugopal8208]

"AA" string is "gwQ=" is it correct?

[@a_Playerwastaken]

2 40 40 37 47 34 29 30 40!

[@svalyavasvalyava9867]

Thank you!!!

[@artahir123]

3:30 why multiple of 4 ?

[@singgihramap5335]

thank you

[@schenken660]

You are welcome :-)

[@alselcukoglu4049]

bro thanks

[@theo-is-drawing5652]

i have a question : how do you translate the six bits segments in values ? please someone answer me

[@andrewkendall7814]

Binary, or Base-2. With 6 bits, from left-to-right, you're looking at positional values of 32-16-8-4-2-1, so 011010 is 16 + 8 + 2 = 26.

[@theo-is-drawing5652]

@@andrewkendall7814 sorry , i'm young and i didn't really understood the explanation