background
MarkDown, as a programmer’s essential tool, eliminates the cumbersome reformatting of rich text editors and allows us to focus on the output of the technology. However, MarkDown also has the disadvantage of storing images. MarkDown files must be a link to use images. Each platform has its own way of storing pictures, and without using a graph bed, the same article posted to different platforms requires a separate upload. This is too much trouble.
The best solution now is to use a map bed to store pictures
Commonly used free map bed summary
| Figure bed | instructions |
|---|---|
| sm.ms | No registration required, overseas server [free] |
| meotu | To register, domestic server [free] |
| Z4a figure bed | To register, domestic server [free] |
| Aggregate figure bed | To register, domestic server [free] |
| NiuTu net | No registration required, Japanese server [free] |
| imgbb | No registration required, Asia-pacific server [free] |
| upload | No registration required, overseas server [free] |
| catbox | No registration required, overseas server [free] |
| Passing figure bed | To register, overseas server [free] |
My choice
[seven niu yun and clap cloud again] need to put on record domain name, still want to spend domain name and server’s money, not cost-effective. [Tencent Cloud and Ali cloud] a wide range of charges, just do a bit of a waste of chart bed. [third party free map bed] unstable, do not know which day closed down. [cloud disk chart bed, social networking site chart bed, cloud note chart bed] as the website is getting bigger and bigger, with more and more people, sooner or later will do anti-chain restriction [self-built chart bed] is not good maintenance, time-consuming and laborious. [code hosting site] itself more secure and stable, speed is also ok, personal use is enough. Based on the above analysis, my graph bed selection is
- Common: Use the Gitee warehouse as a map bed
- Spare: third party free map bed
- Backup (prevent data loss) : Github, Baidu web disk
It is recommended to compress images before uploading, which can reduce space usage and effectively speed up image loading. Good compression tools are as follows
Online tools:
- TinyPNG website
Local tools:
- Format factory
Chart bed management tool
After selecting the image bed, you must upload and use the image, and you will face the problem of having to go to the image bed upload, copy the link, and then go back to the platform where the image is used. Especially troublesome. So here comes the picture bed management tool to help us quickly upload images and get the image URL link. In this way, you can save yourself the tedious operation.
Here are some of the best graphical bed management tools
- PicGo website, PicGo github address (Windows, MAC)
- VScode – PicGo plug-in
- ShareX github shareX github shareX Github shareX Github
- Upic-github address (MAC)
- PicUploader official website, PicUploader- Github address (Windows, MAC)
PicGo is good, but not so good for code clouds. I am a MAC system, so I use uPic, the official website has a detailed user manual, support SMMS, Youpatyun USS, Qiniuyun KODO, Ali Cloud OSS, Tencent Cloud COS, Weibo, Github, Gitee, Amazon S3, custom upload interface. You can also choose to compress the image before uploading. All the compression tools are saved.
Note:
- Note the choice of path in the chart bed Settings, this is equivalent to an album, if you want to save the picture to another album you have to change the path.
- This method uploads each image to the code cloud once, resulting in a lot of commit records. When the amount of personal pictures is not large, there will be the possibility of abusing the code cloud if the amount of pictures is large, and the official may take some measures.