Check a post before you publish it

A post can fail for a simple reason: the image is unreadable, the link is private, or the reader cannot tell what you are asking. Before pressing Post, review the work from the visitor's side. This is a publishing routine, not a way to guarantee engagement.

Read the text without the attachment

The opening sentence should identify the subject. If the attachment is a screen recording, say what is changing on screen. If it is an audio demo, describe the sound you want people to notice. "Here is the before-and-after mix; listen to the bass under the chorus" gives the audience a task. "New thing, check it out" does not.

Read the text aloud. Remove repeated introductions, unexplained initials, and claims you cannot support. If you ask a question, make it answerable. Asking for feedback on one choice usually produces clearer replies than asking whether an entire project is good.

Review the media at phone size

Open the final file, not just the source project. Small labels that look clear in an editor can disappear when an image is reduced to a phone screen. Check crops, orientation, contrast, and whether an important caption sits near an edge. If a crop cuts off the subject, export a version with more space around it.

Listen to the actual audio file before uploading it. Check that the beginning is audible, the ending is intentional, and the export is the version you meant to share. A filename such as "final-final-3" is not proof. For video, inspect the first frame and the full clip; a correct preview does not establish that the export is complete.

Look for private information

Screenshots can reveal email addresses, browser tabs, account identifiers, notifications, or a person's location. A recording can include somebody's voice without their agreement. Remove those details before uploading. Changing a post's visibility after publishing does not recover screenshots someone has already saved.

Choose the intended audience in the composer. Public means someone outside your circle may see the work. Followers-only and private settings serve different purposes; do not treat either as permission to upload another person's private material. Ask the person first or use an example that does not identify them.

Check permissions and credits

Owning a copy of a song, photo, font, or video does not automatically give you permission to redistribute it. Check the relevant license or get permission from the owner. Keep a record of what you were allowed to do. If a license requires attribution, provide it in a readable place, including the source and the required license information.

Credit collaborators accurately. A mention is useful when the collaborator wants to be tagged and has the account you intend to reference. Do not select a similar-looking username or use mass mentions as a promotion tactic.

Open links as a visitor

A project link that works while you are signed in may lead everyone else to an access request. Test the public destination in a separate browser session. Confirm that it opens the right version, uses a recognizable domain, and gives the reader the information promised by your post.

After publishing, open the post once and review it. Correct factual mistakes promptly. If something exposes private information, remove it and contact support if you need help. Do not repeatedly delete and repost a sound post to chase a better position in the feed.