Back to the FAQ
Open the Table of Contents to find your exact case!
Case 1: The text just doesn't get formatted

Why?

This is because the field you're currently editing does not have Markdown enabled or supported. Any other syntax won't be rendered either. This is often reported in Simply Plural.

Common Fixes

Use a Markdown-supported field

Make sure the field you're editing supports Markdown, that it also supports converting text to images and your settings aren't blocking remote content.
This is usually supported in descriptions and custom fields, while NOT on name and pronouns.

Enable Markdown / image support

There are different places to look at depending on what kind of field you're editing:
Name & Pronouns: Not possible
Description: On SP, use the "paint roller" toggle located on the top right corner of the field (in edit mode). Make sure there isn't a strike-through, then test by exiting edit mode.
Custom fields: Go to the "Custom fields" settings, then make sure that Markdown support is enabled for the chosen field.
For Ampersand: Go to Settings -> Security -> Toggle on "Allow remote content".
For Octocon: Image links are not yet supported, but this is planned to be added in the future. Basic Markdown still works there.
Case 2: The text vanishes without render

Why?

If you have a working internet connection, in almost any case of this kind, this is because the service that hosts your linked image (usually Catbox, File garden, …) does not permit its usage in your app. This is due to an enormous amount of images trying to be handled at the same time when an app like Simply Plural tries to download all avatars at once. So it's best you don't use these services for plural purposes and instead rely on the fixes below.

Common Fixes

If possible: Upload to the app / tool directly

In most apps like Simply Plural, Octocon and more, you are given the option to
In few apps like Ampersand, it's possible to locally load media through assets instead of risking your privacy and uploading them online. Local means data doesn't leave your device. The app will provide you options, and usually you would include them with the ![](@Asset-Name) syntax; notice the added @ .
If directly uploading to the app's storage isn't possible in your app, try the other method below.

Switch to a hosting provider that is made for plural usage

We recommend you use ScratchUpload. It is made by a plural system and is made for usage in plural contexts, such as keeping all your avatars. It also comes with great privacy-focused features and firewalls to avoid bot scrappers pulling your images and only allow the services you actually use for downloading them. Everyone can use the site as long as it's useful for them.
Case 3: The render is glitched / a huge grey box

Why?

This is because the Markdown format is invalid in some way - usually, there are hidden characters that you might not be aware of and that would prevent images from working correctly. Did you copy and paste from someone else's template or do you use a non-English keyboard? Both could accidentally make that happen.

Common Fixes

Retype the Markdown

As simple as that:
1.
Delete and type exactly ![]()
2.
Re-copy your image link from the source (test it by opening on a browser).
3.
If the URL leads to the image, then keep this link.
If it's on ScratchUpload, there's a chance you get an "Access Forbidden" error: this is normal and intentional, and you may try using that link regardless.
4.
Paste that link back into your app under () and see if the image loads properly.

Inspect your text

Watch out for any invisible characters that might accidentally get put into your syntax. This is due to using some non-English keyboards and/or text converters such as a stylish text generator. Any of them found inside the image Markdown will break the final render.
Try an Unicode Character Inspector found online where you paste in your text and it will tell you exactly what your text contains. From there you can tell if any unusual Unicode character is found inside what you pasted.