Last Updated on February 25, 2022 by Amit

Redirect fregment URLs using htaccess

I often see users struggling with their RewriteRule to redirect fragment URLs.

Fragment is something that the server doesn’t receive meaning that a URL containing #path  can not be redirected using htaccess or any other server side redirection methods.

Fragment usually appers at the end of the URL and starts with a “#” character.

Anything that comes after # in URL is part of URL fragment.

A fregment is handled client side ( by web browser) and used as jump to navigation link in a web page. 

When  a fragment URL is typed in browser address bar your web browser makes it so that the page automatically  scrolls to the fragment href section on the requested page .

The following is an example  of fragment URL:


In the above URL , /file.php is URL path and #foobar is a fragment.

Your web server only receives the URL path  as request header string and the remaining part (#foobar) is trimmed or not sent. Since the fragment is manipulated client side , your webserver doesn’t get such URL segment and there is no way to handle it server side.
You can redirect fragment URLs using JavaScript or other client side redirect logic. In the last paragraph bellow I will show you how we redirect fragment URLs client-side  with some code examples.

Redirect to a Fragment URL using RewriteRule

It is quite possible to redirect your original URL path to a fragment URL . For example example.com/thispath can be redirected to example.com/#thispath using NE  and R (NoEscape and Redirect) flags in RewriteRule directive. 

example.com/#thispath can not be redirected to example.com/thispath because the requested URL contains # path and its is not manipulated server-side. 

You can’t redirect fragment using htaccess RewriteRule

As I already mentioned fragment is manipulated by web browser and not by server . All you can do to redirect your fragment URL is JavaScript redirect.  I often see users posting questions on stackoverflow regarding #path where they want to redirect fragment URLs to a custom path . For example /path/#foobar to /newpathWithoutFregment and the RewriteRule they try is something like :

RewriteRule ^path/#foobar /newpathWithoutFregment [R]

The rule above will never work because of the following two reasons :

  1. # is a special character in mod-rewite as it is used to add comments in RewriteRule.
  2. # is a fragment which is maintained by browser  and its not sent to the server.

The rewiteRule above won’t work even if you escape the # character as its not even sent to the server. 

The following Rewriterule works  perfectly fine


You can redirect your URL path to fragment using NE and R flag.

Here is a RewriteRule example to redirect /foobar to /#foobar :

RewriteRule ^foobar /#foobar [NE,R]

The above example works because here you are redirecting your NonFregmentPath to a FragmentPath. You type the path /foobar into your browser, your browser then sends the path to server , server receives the path , reads htaccess rules and then issues a Redirect (/foobar => /#foobar) to your webbrowser . And finally your web browser makes the hash redirection.

The NE flag is important in the rule above.  Without NE the # gets encoded to its hex value which may end up in an incorrect or not found path.

JavaScript based solution to redirect fragment URLs

Since JavaScript is a client scripting language and works on web browser, you can easily redirect your fragment URLs using JS window.location.assign() property . The following is a simple one liner code to redirect /#foobar to http://example.com/#foobar .


The window.location.hash() property returns the current page hash ie #foobar in this example.

You can learn more about JS location pproperties on the official Mozilla site here .

I hope the post was helpful. Thank you so much for reading.

How useful was this post?

Click on a star to rate it!

Average rating 4.5 / 5. Vote count: 185

No votes so far! Be the first to rate this post.