Signatures on Wikipedia identify you as a user and your contributions to Wikipedia. They encourage civility, collaboration, and communication by identifying the author of a particular comment and the date and time at which it was made. Because of that, having an uncivil signature (especially one that makes any kind of personal attacks toward someone else) is prohibited and, in some cases, the user will be blocked from editing until the signature is changed. In most cases, anything that is not allowed as an account's username (in whole or in part) is also not allowed to be in a signature either.

Furthermore, signatures also serve a technical purpose: various user scripts and talk-page archiving bots, including lowercase sigmabot III, rely on their timestamps to know when to archive old threads. It's because of this that it's also important to not change the timestamp of any signatures, as doing so can lead to stale threads persisting longer, and after they would've otherwise been archived.

Any posts made to any type of discussion page must be signed (this does not include adding WikiProject boxes and other such administrative templates). Note that, as stated below, if you choose to edit those kinds of pages without logging in, then you should still sign your posts—regardless of whether or not you have an account. Edits to articles must not be signed, as signatures on Wikipedia are not intended to indicate ownership or authorship of any article. Instead, the page history identifies who made edits. Signatures do not translate from ~~~~ in edit summaries. In other instances, and when posts should not be signed, specific instructions are provided to specify this on the specific page. Files that are used in articles, including image and sound files, should also not contain any signatures.

When using the reply tool or new topic tool, the software will automatically sign your post. (If you type a signature anyways, it will remove the duplicate.)

Preferred option edit

Standard signature edit

There are three ways to sign your posts manually:

1. At the end of your comments simply type four tildes (~), like this: ~~~~.
2. If you are using the edit toolbar option (by default, it appears above the edit box), click the signature icon^{[Note 1]}   to add two hyphens and four tildes like this: --~~~~.
3. Use the reply tool or new discussion tool that are available as beta features in your user preferences. Both of these features will automatically insert a signature, without needing to add any wikicode.

The four tildes will be automatically replaced with your signature after you have published the changes, as follows:

Since typing four tildes adds the time and date to your resulting signature, this is the preferred option for signing your posts in discussions.

Note that if you choose to contribute without logging in, regardless of whether you have an account, you must still sign your posts. In this case, your IP address will take the place of a username, and will link to your contributions history. Your IP address will look like something similar to 192.0.2.213 or 2001:DB8:CEEE:21B:DB60:07FE:4277:63FF.

If, for some reason, you are not getting the above results when signing, see the SineBot Frequently Asked Questions for tips.

Other options edit

Using three tildes edit

Typing three tildes results in the following:

However, since this does not date-stamp your signature, you may wish to sign this way only when leaving general notices on your user page or user talk page. This is also a convenient shortcut (rather than typing out the full code) when you want to provide a link to your user page.

Using five tildes edit

Typing five tildes will convert to a date stamp with the current date and time, without adding your signature, like this:

In general, when communicating with others, you should use one of the previous options and not only a timestamp. There are exceptions to this: such as when requesting assistance from the Third Opinion project, the requested format for signing is the five tilde signature, to slightly help improve neutrality from the responding volunteer. A timestamp may also be used when updating one of your submitted posts on a talk page by appending (updated ~~~~~) to your already existing signature.

In some templates, this is the preferred way to add the date.

Every editor's default signature (as defined by MediaWiki:Signature) will display when ~~~~ is typed. This looks like:

Example (talk) 12:39, 18 April 2024 (UTC)

Unregistered users, or users not logged in, may choose to manually sign with a pseudonym or tag (e.g. anon.), as their IP address will be stored in the page history. If you choose to sign your posts in such a way, you must still finish your signature with four tildes (such as Anonymous editing as ~~~~) to help aid others with reading the thread easily, and with communicating back with you.

Customizing how everyone sees your signature edit

Registered users can customize their signatures by going to Special:Preferences and changing the field "Signature". This changes the signature that is left when you enter ~~~~ into discussions. It can be used to sign your posts with a nickname, or with custom formatting, or both.

This technique only applies where you have left your signature onto a page while logged into your account. It also doesn't affect how your username appears in your watchlist, in any logs or page histories, or where someone else has added a link to your user page in a discussion. Modifying your signature in your user preferences will only apply to the future signatures that you leave moving forward. Since adding ~~~~ to discussions simply results in those characters being replaced by your signature before the edit is saved, any existing signatures that you've left on previous or existing discussions will not be automatically updated or changed.

Treat as wiki markup edit

If you do not check the "Treat the above as wiki markup" box, the exact content you enter will be used as your signature. For example, if User:Example had set their signature to read <span style="color:#C00000">NICKNAME</span>, thereafter the signature (generated when they mark a post with ~~~~) would be:

<span style="color:#C00000">NICKNAME</span> (talk) 12:39, 18 April 2024 (UTC)

If you do check the "Treat the above as wiki markup" box, you can describe your signature using "raw" wikitext (such as <span> and wiki-markup) which will be substituted unchanged when you sign your posts. If User:Example had set their signature to read [[User:Example|Ex@''mple'']]<sup>[[User talk:Example|t@lk]]</sup>, the signature generated by ~~~~ would be:

Ex@mple^t@lk 12:39, 18 April 2024 (UTC)

In this case, you are responsible yourself for linking to your user page (e.g. User:Example).

To visibly include the pipe (|) or equals (=) characters in your signature, you must escape them, or they will break templates unexpectedly when your signature is present. To escape the | symbol, use the following special code: | (including everything from the ampersand to the semi-colon). To escape the = character, use =.

Putting two or more exclamation points (!!) in a row in your signature can break tables in which your signature appears. Use !! as a substitute in order to avoid having two exclamation points in a row.

Customizing how you see your signature edit

To change how your signature appears to you, e.g. to make it easier to spot, without affecting how it appears to other users, you can create a personal CSS style sheet. For example, to display your username in bold white text on an orange background (like Your username), add the following to Special:MyPage/common.css, replacing Your username with your actual username:

#bodyContent a[title="User:Your username"] { background-color: #ffa500; color: #ffffff; font-weight: bold; }

When you use this technique, bright colors can help you to more quickly scan long pages that contain [[User:Your username]], including Talk pages, page histories, your watchlist, and if anyone links to you in a discussion. Colors to use for this can be researched via the Web colors article, and you can update your common.css file at any time to modify the display style.

Guidelines and policies edit

Because these signatures are seen by everyone, be aware of the guidelines and policies summarized below:

• It is common practice for a signature to resemble to some degree the username it represents.^{[Note 3]}
• Do not impersonate other users.
• Do not use images, transcluded templates, Lua modules, parser functions, TemplateStyles or external links in your signature.
• A distracting, confusing, or otherwise unsuitable signature may adversely affect other users. For example, some editors find that long formatting disrupts discourse on talk pages, or makes working in the edit window more difficult.
• Complicated signatures contain a lot of code ("markup") that is revealed in the edit window, and can take up unnecessary amounts of narrative space, which can make both reading and editing harder.
• Always keep the time/date-stamp: these are used by bots to determine when a discussion is eligible to be archived.

Syntax guidance edit

If you attempt to save a signature with certain types of errors, you will see an error message. These errors can be a little tricky to diagnose, but here are some tips:

• Each opening tag must have a corresponding closing tag. Example: each <b> needs a matching </b>. This applies to '' and ''' markup as well.
• Tags must be "nested" correctly. Example: <b>User:<i>Example</i></b>, not <b>User:<i>Example</b></i>.
• If an opening tag appears within a wikilink, it must be closed within a wikilink. Example: [[User:'''Example''']], not [[User:'''Example]]'''.
• Your signature must include a link to your user page, talk page, or contributions. At least one of the three must be on the same Wikimedia project as the page where the signature is used.^{[Note 4]} (This is a technical requirement enforced by the MediaWiki software.)

Signature forgery edit

Never use another editor's signature. Impersonating another editor by using their username or signature is forbidden. Altering the markup code of your signature to make it look substantially like another user's signature may also be considered a form of impersonation. Editing the code of your signature to link it to another editor's user page is not permitted. It is also ineffective, as the change log of the page records the IP address and (if applicable) username of all editors; as such, any impersonators can easily be caught if the signature in the diff view differs from the editor's default signature. While not an absolute requirement, it is common practice for a signature to resemble to some degree the username it represents.

If you encounter a user whose signature is disruptive or appears to be impersonating another account, it is appropriate to ask that user to consider changing their signature to meet the requirements of this policy. When making such a request, always be polite, and assume good faith; do not immediately assume that the user has intentionally selected a disruptive or inappropriate signature. If you are asked to change your signature, please avoid interpreting a polite request as an attack. Since the success of Wikipedia is based on effective teamwork, both parties should work together to find a mutually acceptable solution.

Appearance and color edit

Your signature must not blink, scroll, or otherwise cause inconvenience to or annoy other editors.

• Avoid markup such as <big> and <span style="font-size: 200%;">^{(or more)} tags (which enlarge text); this is likely to disrupt the way that surrounding text displays.
• Do not add line breaks (<br />), which can also negatively affect nearby text display. The use of non-breaking spaces or <span class="nowrap"> to ensure that the signature displays on one line is recommended.
• Be sparing with subscript and superscript. In some cases, this type of script can also affect the way that surrounding text is displayed.
• Do not make your signature so small that it is difficult to read.
• As some users have vision problems, be conscious of color and contrast issues. If you use different colors in your signature, please ensure that the result will be readable by people with color blindness, defective color vision, and other visual disabilities.^{[Note 5]}
• Do not include horizontal rules (---- or <hr />).
• Do not include <div>...</div>s because those cause the surrounding text to make a new line.

For guidance on how to use color and other effects to customize the appearance of your signature, see this tutorial.

Signature formatting has been the subject of numerous Requests for Comment, and has also resulted in some very heated debates by some of the editors involved, and on both sides of the discussion. When dealing with potentially problematic signatures, simply being polite is often sufficient and can prevent the situation from escalating into a dispute.

Borrowing designs edit

Editors do not own the design of their signature and cannot prohibit others from borrowing it. However, because signature customization is intended in part to make it easier to tell editors apart, it is considered good practice when borrowing a signature design to change the color or another design element.

Font tags edit

<font>...</font> tags were deprecated in HTML4 and are entirely obsolete in HTML5. This means that the popular browsers may drop support for them at some point. Wikipedia is already preparing for this by delinting code project-wide through Linter, and by disallowing obsolete tags in new signatures. When support is finally dropped, the tags will be ignored in all existing signatures; any properties such as color and font family will revert to their default values. For this reason, it is recommended that you use <span>...</span> tags and CSS properties instead. For usage examples, see Wikipedia:Signature tutorial § Real-life examples. You may request additional coding assistance at Wikipedia:Help desk.

When you change your signature, it does not affect signatures that you used on pages in the past. Therefore, if you currently use <font>...</font> tags in your signature, switching to <span>...</span> tags now will reduce the number of your signatures (including those in the archives of talk spaces) that will render incorrectly after the browsers drop support for <font>...</font>. Moreover, refactoring old signatures from you and other users (including in archive pages) by changing <font> tags to <span> tags can help prepare the project for this eventual loss of support.

Images edit

Images of any kind must not be used in signatures for the following reasons.

• Excessive or large images can cause issues for users on low-performance devices.
• A new image can be uploaded in place of the one you chose, making your signature a target for possible vandalism
• They make pages more difficult to read and scan
• They make it more difficult to copy text from a page
• They are potentially distracting from the actual content
• Images do not scale with the text, making the lines with images higher than those without them
• They clutter up the "file links" list on the respective image's page every time one signs on a different talk page
• Images in signatures give undue prominence to a given user's contribution

Unicode symbols (including emoji) may be used in your signature, as long as the signature complies with the other guidelines on this page.

Length edit

Keep signatures short, both in display and in markup.

The limit is 255 characters.

Extremely long signatures with a lot of HTML/wiki markup make page editing and discussion more difficult for the following reasons:

• Signatures that take up more than two or three lines in the edit window clutter the page and make it harder to distinguish posts from signatures.
• Long signatures give undue prominence to a given user's contribution.
• Signatures that occupy more space than necessary in the edit box displace meaningful comments, thus forcing editors to scroll when writing their replies.
• The presence of such long signatures in the discussion also disrupts the reading of comments when editors are formulating their replies.

The software will automatically truncate both plain and raw signatures to 255 characters of code in the Signature field. If substitution of templates or another page is used, please be careful to verify that your signature does not violate the 255-character length limit when the templates are expanded, as the software will not do this automatically.

Overriding custom signatures edit

Unclutter signature minimiser edit

If you prefer not to see other users' custom signatures, you can use the custom JavaScript module Unclutter. By default, Unclutter scans non-special non-article pages for timestamped signatures, wraps them up and replaces with a text of the form:

— Example (annotation) (talk • ctb • act • log • sig)

This technique displays the actual username to you and is extensively configurable. It doesn't affect how anyone else sees the signatures. See User:Kephir/gadgets/unclutter for more details.

While this script works in practice for most signatures found on the English Wikipedia, there are several unavoidable limitations which make Unclutter fail to recognise every possible signature. Signatures which violate policies laid out on this page may not be recognised. Unclutter is not an excuse to violate or decline to enforce the signature policy.

Using custom CSS edit

It's also possible to use your personal common.css style sheet to override the formatting of other users' signatures.

This allows you to decide how links to user pages should be displayed to you when you are logged-in. For example, you could highlight Your username in bold reversed mauve and Other signatures in normal mauve. This approach works by reversing a variety of commonly used signature formatting techniques, but it doesn't attempt to replace the text content of the signature. For example, if User:Example has customized their signature to read Ex@mple, changing the formatting would display Ex@mple rather than their actual name Example.

No other users will see your custom effects. You can remove or modify them at any time by changing the instructions in your style sheet. The change will apply to all pages regardless of how old they may be. For an example stylesheet, see User:Pointillist/reformat-signatures.css.

Internal links edit

Signatures must include at least one direct internal link to your user page, user talk page, or contributions page; this allows other editors easy access to your talk page and contributions log. The lack of such a link is widely viewed as obstructive.

If, while making modifications, you accidentally disable this link, see Help:How to fix your signature. When you insert your signature on your talk page or user page, a link to that page will appear black, bold and inactive, so test your signature elsewhere, such as the sandbox.

Disruptive links edit

It is better to put information on your user page rather than in your signature. Brief additional internal links are generally tolerated when used to facilitate communication or to provide general information, but undesirable if seen as canvassing for some purpose.

Do not place any disruptive internal links (especially when combined with custom formatting, for example CLICK HERE!!!) in your signature.

External links edit

Do not include links to external websites in your signature.

Mass posting of links to a particular website is strongly discouraged on Wikipedia. Posting a link to an external website with each comment you make on a talk page could be taken as link spamming, or an attempt to improve your website's ranking on search engines (which doesn't actually work in the first place). If you want to tell other Wikipedians about a website with which you are associated, you can do so on your user page.

The templates {{unsigned}} and {{unsigned IP}} can be used at the end of an unsigned comment to attach the username or IP to the comment. None of these templates automatically populates (fills in) the username or IP of the poster or the time of the post. That information is best copied from the history page and pasted into the following templates. All of the unsigned templates must be substituted.

The templates {{unsigned2}} and {{unsignedIP2}} do almost the same as {{unsigned}} and {{unsigned IP}} when used with two parameters, but the ordering of the parameters is reversed. The resulting display is the same. These templates may be useful when copying and pasting from the edit history, where the timestamp appears before the username.

The template {{xsign}} is a wrapper for {{unsigned}} and {{unsigned IP}} that will parse the username and date string copied and pasted directly from the edit history. The resulting display is the same.

It is also a good idea to notify users, especially new users, that they should sign their comments. You may use the template {{uw-tilde}} on the user's talk page or one of the welcome messages for new users.

Also, the template {{undated}} can be used at the end of comments where the user gave their username but no timestamp: