I don't know if this is a commonly known method for getting free Wordpress content or not, I just figured this out on my own yesterday. Yes, you can go to torrents or sketchy sites (or BHW's downloads section) to download Wordpress plugins or themes if you don't have the money to pay for them. Though as a developer myself, I recommend you pay! Downloading PHP files and just putting them on your server is very dangerous if you aren't code literate, even if you run them through a VirusTotal check. They could be modified to steal data or do other things you aren't anticipating. But... Why take the risk when you can take advantage of the fact that there are a lot of terrible developers on Github? It seems like many Wordpress developers or website owners haven't learned what the .gitignore file does. And as a result... Yes, that's right. Over 17,000,000 files in Github are located within a wp-content/plugins folder. And a lot of those files are plugin files that belong to paid plugins. The same goes for themes. So if I want to find the most popular paid Wordpress theme, Avada... Or if I want the plugin Revolution Slider Go to the repository show in a given search result, then click on the Download as ZIP once you've verified the files are there. This specific repository was updated recently (likely indicating up to date themes and plugins), and as you can see, there are multiple premium plugins available! ALWAYS use the in path search operator. Otherwise all HTML files or template files that reference something in the theme/plugin will show up, these don't always indicate that the user also uploaded the themes or plugins folder. More Tips! 1. Sort by most recent to get the current versions of themes and plugins. 2. Not every theme or plugin is available, but this is a good place to start looking! 3. Usually the newest versions aren't on Github immediately, but it just depends. 4. Github's search isn't complete, you can't do exact match search or have many basic operators. Here are search operators you can use: Code: https://help.github.com/articles/searching-code/ 5. Searching shows every file for every instance. So if at theme has 200 files within it, that means 200 results will trace back to a specific theme in a specific repository. You usually will want to skip through the results pages at a time. 6. You may want to check commit history of some of the files. They may have customized a theme without using the child theme or something like that. 7. To quickly determine what version of a theme/plugin you've discovered is, simply look for a README or text file within that theme/plugin's main folder. Most have that information, or it is within the comments of every theme/plugin file. Let me know how this works for you!