image resize in github flavored markdown.

image.resize.in.github.flavored.markdown.md

Image source

https://gyazo.com/eb5c5741b6a9a16c692170a41a49c858.png

Try resize it!

• ![](https://gyazo.com/eb5c5741b6a9a16c692170a41a49c858.png | width=100)

  • 

• ![](https://gyazo.com/eb5c5741b6a9a16c692170a41a49c858.png =250x250)

  • 

• ![](https://gyazo.com/eb5c5741b6a9a16c692170a41a49c858.png)

  • Copy <img> in browser DevTools. Replace ![](url) to <img>. Add width(and height) attr.
  • <img src="https://camo.githubusercontent.com/..." data-canonical-src="https://gyazo.com/eb5c5741b6a9a16c692170a41a49c858.png" width="200" height="400" />
  • 

Other information

• Resize image in the wiki of github using markdown
• how to change image size markdown

🫠 🫠 🫠 🫠

Markdown alone doesn't support resizing images, but you can try this (some platforms support it):

![Description](image.jpg){width=300 height=200}

However, this syntax is not widely supported. Using HTML (<img>) in your markdown file is more reliable.

<img src="image.jpg" alt="Description" width="300" height="200">

It worked for me. Thanks @kaecy

{width=300 height=200}

Doesn't work for Github comments tho RIP

From this:

📅 2024-11-21	📅 2024-11-01
🏷️ Fundamental, Blockchain, Y-Intelligence	🏷️ Fundamental, AI, Y-Intelligence
🔗 Read More	🔗 Read More

To this:

🖋️ Introduction to Decentralised Science (DeSci)	🖋️ Introduction to Artificial Intelligence
📅 2024-11-21	📅 2024-11-01
🏷️ Fundamental, Blockchain, Y-Intelligence	🏷️ Fundamental, AI, Y-Intelligence
🔗 Read More	🔗 Read More

The code:
<img src="https://y-intelligence.vercel.app/_astro/cover.mwFkbjT1_uQDX9.webp" width="300" height="200"> | <img src="https://y-intelligence.vercel.app/_astro/cover.Bwzr-ZZT_CmAPP.webp" width="300" height="200">

The code: <img src="https://y-intelligence.vercel.app/_astro/cover.mwFkbjT1_uQDX9.webp" width="300" height="200"> | <img src="https://y-intelligence.vercel.app/_astro/cover.Bwzr-ZZT_CmAPP.webp" width="300" height="200">

@Laoode
Yep, when resizing images in Markdown, HTML tags are the way to go (until/unless something changes).
A bit unfortunate since Markdown linters don't care for inline HTML... 🤷‍♂️

@kaecy That worked for me in an Issue post, thanks.