Skip to main content

Possible with a plugin

Not all feature requests can be implemented. Why?

Keeping things light

Some issues here are feature requests or "is it possible to do this and that" requests.

One of the primary goal of YOURLS is to achieve balance between features and efficiency. In other words, to keep it as light as possible while being powerful. In other words, to keep away from bloating core with features that won't be used by many.

So, yes, feature requests are often closed with the "plugin domain" label.

Don't modify core files

That's idiotic and will get you in trouble. Don't hack core. Make plugins instead.

There is a plugin API for this

Most of the time, features that are requested won't be implemented into core, but are easily implementable with a plugin. That's the whole point of the plugin API that has been introduced in YOURLS.

There may be already a plugin for this

Head to to check if someone already coded a plugin with this feature, or get that plugin coded by someone who coded a similar plugin.

Find a plugin coder

If you can't code yourself and want a feature implemented, you need to find a plugin coder.

An option is to head towards freelancer sites (,, etc.) and post your project. You should get very affordable quotes.

Another option, that includes quality, full YOURLS code knowledge and future-proof coding, is to ask me (Ozh, contact me offsite by mail, ozh at ozh dot org) for a quote. Depending on the project and my free time, I may be able to help you.

Find plugin ideas

If you can code (it's fun!) and look for ideas, browse through the issues labelled with plugin. You will find there people with real use case and needs!