WP:RFD states: "Redirects are cheap. Redirects take up minimal disk space and use very little bandwidth. Thus, it doesn't really hurt things if there are a few of them scattered around." A redirect page may even avoid the creation of duplicate articles on the same subject, and actually save disk space.

1. Because "deleted" pages are hidden from public view and not actually erased from the database, deleting the redirect will not save any disk space, and in fact actually consumes space slightly due to writing to the deletion log (although this is very minor). Concerns about the servers' performance are in any event largely irrelevant to the work of editors.
2. However, this does not mean we should pre-emptively create redirects for their own sake. See Wikipedia:Redirect for more.
3. On the other hand, cross-namespace redirects make processing Wikipedia content more complex for bots and scripts.
4. Creating redirects can help preserve the option of splitting an article when desired; candidates for such include articles dealing with a geographical topic with different names at differing periods of history, articles that are set indices, or articles that cover multiple characters in a book (see MOS:REDIR).
5. Creating redirects from existing articles can be valid alternatives to pursuing deletion discussions, saving discussion time where a redirect is a legitimate and likely outcome. Consensus should still be sought via discussion (or the BOLD, revert, discuss cycle, for less contentious topics).

• Wikipedia:Redirect instead
• Wikipedia:Redirects are costly
• Wikipedia:Disambiguations are cheap
• Wikipedia:Hatnotes are cheap
• Wikipedia:Redirect, DAB entry or hatnote needed
• Meta:Don't delete redirects
• Meta:Redirectionism