Envato Marketplace Wiki » CodeCanyon

CodeCanyon: Apps Upload Instructions

jeffrey — Tue, 14 Jun 2011 18:52:13 +0000

Ensure You Are Using Acceptable Images/Extras:It is up to you to ensure that all images/assets in your project are cleared for use. If necessary, you should contact the creator of the asset and ask them.
As an example, images from the stock photography site iStockPhoto are generally not usable in templates unless you have purchased an extended license for the item. In this instance you would report the extended license details in the comments section.

Please review this article for more information on acceptable assets.
- DO NOT submit an app that isn’t focused on improving workflow for web developers. For example, a Flickr browser app would not be accepted, while a Compresser or HTML5 Boilerplate GUI would be.
- DO NOT copy and paste code from various tutorials around the web. You’re of course free to gain inspiration and to learn techniques, however, that’s the extent of what you should be using a tutorial demo for.
- DO test your app in various OS versions to ensure that it works as far back as possible.
- DO include as much documentation as is necessary for your item. Otherwise, you’ll pay the price when you receive countless support emails. Documentation is key.
- DO feel free to record short video clips to demonstrate the functionality of your item. Sites like Screenr offer free recording and hosting tools, which are wonderfully simple to use.
- DO code in a style that follows the latest best practices in the industry. Otherwise, your item will be rejected accordingly.

Follow These Guidelines:

Create the Final Download File:You should create a single ZIP file that contains the final app for download, along with any applicable documentation.
All Files Must Contain a Help File: All items sold on CodeCanyon must contain documentation explaining how to customize, install and use the item. If you deem it necessary, as noted above, take a few moments to record quick screencasts with a free service, like Screenr. This can drastically reduce the number of support questions that you could potentially receive. You can refer here for a documentation template that you’re free to use.
Create a Preview Zip:Include several screenshots which illustrate the functionality of your app. It’s essential that you provide plenty of images if you choose to forgo a live preview. Screenshots should be JPGs, should be no larger than 1200px in width, but can be any height. You can have up to 10 screenshots of the item, and each screenshot may have a description attached. Here’s how you set up the file:
1. Name each screenshot in sequence as number_Title.jpg. E.g. 1_Homepage.jpg, 2_Generalpage.jpg.
2. Create optional .TXT files containing a few lines of descriptive text, with the same name as the screenshot. E.g. 1_Homepage.txt, 2_Generalpage.txt.
3. ZIP up the JPGs and TXTs together into a single ZIP file.
Create a 590px Wide Image Preview This will be the featured image, when a user visits your item page. This is the first thing they see, so make sure that it’s effective. If you’re not a designer, use these PSD image templates, and substitute your item’s information.
Create a JPEG Thumbnail:Finally create an 80px x 80px JPG thumbnail for your file. The thumbnail should represent your item in some way. Further, many authors add a small dose of branding, in some form, to each of their item’s thumbnails.
Upload your files to CodeCanyon!

CodeCanyon: Mobile Upload Instructions

jeffrey — Tue, 09 Nov 2010 22:26:34 +0000

Ensure You Are Using Acceptable Images/Extras:
It is up to you to ensure that all images/assets in your project are cleared for use. If necessary, you should contact the creator of the asset and ask them.

As an example, images from the stock photography site iStockPhoto are generally not usable in templates unless you have purchased an extended license for the item. In this instance you would report the extended license details in the comments section.

Please review this article for more information on acceptable assets.
Follow These Guidelines:
1. DO try to make your submission as cross-mobile compatible as possible, if submitting to the “Native Web” category. However, we certainly understand that this simply isn’t possible across the board for. Nonetheless, at least try to provide some level of support for as many mobile browsers as possible.
2. DO NOT copy and paste code from various tutorials around the web. You’re of course free to gain inspiration and to learn techniques, however, that’s the extent of what you should be using a tutorial demo for.
3. DO validate your code, in order to catch any small mistakes in your mark-up. With that said, don’t worry about any CSS3/HTML5 related errors…because they aren’t errors! :)
4. DO include as much documentation as is necessary for your item. Otherwise, you’ll pay the price when you receive countless support emails. Documentation is key.
5. DO NOT specify that your mobile component/theme works in a certain browser if it, in fact, does not.
6. DO NOT assume that the buyer of your item has any significant level of coding knowledge. When preparing your documentation, treat the buyer like a three year old. They’ll thank you for it!
7. DO specify in your live preview which browsers it is optimized for.
8. DO feel free to record short video clips to demonstrate the functionality of your item. Sites like Screenr offer free recording and hosting tools, which are wonderfully simple to use.
9. DO code in a style that follows the latest best practices in the industry. Otherwise, your item will be rejected accordingly.
Create the Final Download File:
You should create a single ZIP file that contains the final files for download, any documentation and any auxiliary files such as extra images. This is the file that a user will get when they buy your item. Make it as complete as possible, and organize your file structure into as many folders as is necessary. For example, you might have “Source,” “Demo,” and “Documentation” folders in your final zip file. Simply placing all scripts, images, and documentation within the root of your directory is not acceptable, and is grounds for rejection.

All Files Must Contain a Help File: All items sold on CodeCanyon must contain documentation explaining how to customize, install and use the item. Especially for the components category, you must ensure that you’ve adequately detailed the necessary steps that need to be followed in order to implement your component into the buyer’s project. If you deem it necessary, as noted above, take a few moments to record quick screencasts with a free service, like Screenr. This can drastically reduce the number of support questions that you could potentially receive. You can refer here for a documentation template that you’re free to use.
Create a Preview Zip:
Include several screenshots which illustrate the functionality of your component. It’s essential that you provide plenty of images if you choose to forgo a live preview. Screenshots should be JPGs, should be no larger than 1200px in width, but can be any height. You can have up to 10 screenshots of the item, and each screenshot may have a description attached. Here’s how you set up the file:
1. Name each screenshot in sequence as number_Title.jpg. E.g. 1_Homepage.jpg, 2_Generalpage.jpg.
2. Create optional .TXT files containing a few lines of descriptive text, with the same name as the screenshot. E.g. 1_Homepage.txt, 2_Generalpage.txt.
3. ZIP up the JPGs and TXTs together into a single ZIP file.
Create a 590px Wide Image Preview
This will be the featured image, when a user visits your item page. This is the first thing they see, so make sure that it’s effective. If you’re not a designer, use these PSD image templates, and substitute your item’s information.
Create a JPEG Thumbnail:
Finally create an 80px x 80px JPG thumbnail for your file. The thumbnail should represent your item in some way. Further, many authors add a small dose of branding, in some form, to each of their item’s thumbnails.
Upload your files to CodeCanyon!

Make more money by double dippin’

lance — Thu, 28 Oct 2010 03:09:56 +0000

There are many factors involved when it comes to being a top author, but one of the big ones is using your time efficiently. This isn’t like a normal job where you can zone out for an hour and still collect the same paycheck. If you’re not working, you’re not making money. On the other hand, if you can do twice as much in the same amount of time, you can make twice as much.

One technique I like to use to improve my stock output is double dippin’. What do I mean by that? I mean do the work once and get paid for it twice or more. Here’s an example: One of my very first stock items was an illustration of a clock face. Most authors would stop there and move on to the next file. Instead, I created a Flash version of the clock. With the same graphics and similar code I built a set of Flash timezone clocks. ActionScript is pretty similar to JavaScript so I also built a Unity3d version and have a jQuery one in the works. Did I stop there? No, that same clock is on the wall of my Flash Fine Art Gallery. Did I stop there? Well… yes, but I’m sure it’ll show it’s face again on the Envato marketplaces.

You may be saying – “That’s all fine and good, but how does this apply to me?” This concept can work on just about all of the marketplaces. It even makes sense between different files on the same marketplace. Here are some double dippin’ ideas:

WordPress, HTML, and Flash Developers

Create customizable scrollbars, contact forms, and image galleries (in classes if you’re using Flash).
Reuse modified versions in every theme or template you create. If necessary, improve them, but try not to start from scratch unless it’s absolutely necessary.

Unity3d Developers & 3d Modelers

The Unity3d category on ActiveDen and the 3d Model category on 3dOcean go hand in hand. If you create a 3d model and upload it to 3dOcean, why not bring it to life in Unity and sell it on ActiveDen?

Image Galleries

Create your gallery.
Use screenshots of your other files to populate the gallery in the preview file. First of all, it makes your gallery look nice. Also, even if they don’t buy your gallery, they may still buy your other files!

Textures

Did you know that 3dOcean and GraphicRiver both sell textures? The requirements differ slightly, but there’s no reason you shouldn’t consider uploading all your textures to both sites.

For Anyone

Write a premium tutorial for any of the Tuts+ sites.
Sell that same tutorial on the Tuts Marketplace.
Use what you taught in the tutorial to make a file, add to it to make it unique, and sell it on ActiveDen, 3dOcean, or whatever Envato marketplace it would fit best on.

WordPress, HTML Developers

If your template got accepted to ThemeForest, the design would have to be pretty great. If so, why not upload the design to the PSD Templates category?

This list of examples is by no means complete. I’m sure there are dozens of other ways to double dip. This article is just to get the wheels turning. Just remember, selling stock is all about working efficiently. If you reuse your work, you’ll save time and make more money!

Do you double dip? Show us here: http://activeden.net/forums/thread/do-you-double-dip/33768

CodeCanyon: HTML5 Upload Instructions

jeffrey — Fri, 27 Aug 2010 01:36:10 +0000

Ensure You Are Using Acceptable Images/Extras:
It is up to you to ensure that all images/assets in your project are cleared for use. If necessary, you should contact the creator of the asset and ask them.

As an example, images from the stock photography site iStockPhoto are generally not usable in templates unless you have purchased an extended license for the item. In this instance you would report the extended license details in the comments section.

Please review this article for more information on acceptable assets.
Follow These Guidelines:
1. DO try to make your submission as cross-browser compatible as possible. However, we certainly understand that this simply isn’t possible across the board for an HTML5 category. Nonetheless, at least try to provide some level of support for older browsers, like Internet Explorer 8 and below.
2. DO ensure that your submission uses HTML5 before submitting to this category. This will include using the new HTML5 elements, as well as any applicable JavaScript APIs. Otherwsise, your submission should be submitted to our “JavaScript” category instead.
3. DO NOT copy and paste code from various tutorials around the web. You’re of course free to gain inspiration and to learn techniques, however, that’s the extent of what you should be using a tutorial demo for.
4. DO validate your code, in order to catch any small mistakes in your mark-up. With that said, don’t worry about any CSS3/HTML5 related errors…because they aren’t errors! :)
5. DO include as much documentation as is necessary for your item. Otherwise, you’ll pay the price when you receive countless support emails. Documentation is key.
6. DO NOT specify that your HTML5 item works in a certain browser if it, in fact, does not.
7. DO NOT assume that the buyer of your item has any significant level of coding knowledge. When preparing your documentation, treat the buyer like a three year old. They’ll thank you for it!
8. DO specify in your live preview which browsers it is optimized for.
9. DO code in a style that follows the latest best practices in the industry. Otherwise, your item will be rejected accordingly.
Create the Final Download File:
You should create a single ZIP file that contains the final files for download, any documentation and any auxiliary files such as extra images. This is the file that a user will get when they buy your item. Make it as complete as possible, and organize your file structure into as many folders as is necessary. For example, you might have “Source,” “Demo,” and “Documentation” folders in your final zip file.

All Files Must Contain a Help File: All items sold on CodeCanyon must contain documentation explaining how to customize, install and use the item. Especially for the components category, you must ensure that you’ve adequately detailed the necessary steps that need to be followed in order to implement your component into the buyer’s project.
Create a Preview Zip:
Include several screenshots which illustrate the functionality of your component. It’s essential that you provide plenty of images if you choose to forgo a live preview. Screenshots should be JPGs, should be no larger than 1200px in width, but can be any height. You can have up to 10 screenshots of the item, and each screenshot may have a description attached. Here’s how you set up the file:
1. Name each screenshot in sequence as number_Title.jpg. E.g. 1_Homepage.jpg, 2_Generalpage.jpg.
2. Create a .TXT file containing a few lines of descriptive text, with the same name as the screenshot. E.g. 1_Homepage.txt, 2_Generalpage.txt.
3. ZIP up the JPGs and TXTs together into a single ZIP file.
Create a JPEG Thumbnail:
Finally create an 80px x 80px JPG thumbnail for your file. The thumbnail should represent your item in some way.
Create a 590px Wide Image Preview
This will be the featured image, when a user visits your item page. This is the first thing they see, so make sure that it’s effective. If you’re not a designer, use these PSD image templates, and substitute your item’s information.
Upload your files to CodeCanyon!

CodeCanyon: Common Rejection Factors

jeffrey — Tue, 13 Jul 2010 19:03:04 +0000

Before submitting your first template to CodeCanyon, consider the following factors, which frequently contribute to rejected submissions. Please note that this list should only be used only as a guideline.

CSS Rejections

Low Quality: The most obvious: sometimes, the design simply isn’t of a high enough quality to warrant being sold as a Premium item.
Too General: Because many CSS files are available around the web for free, items must distinguish themselves, and go above and beyond what’s typical.
Similarity: If a new submission is far too similar to items that are already available on the marketplace, it will be rejected. To be accepted, yours must be either unique, or of a higher quality than the currently existing items.
Inline CSS: Do not use inline CSS. Export all styling to an external stylesheet.
Validation: Excluding any vendor-specific prefixes, all of your code must validate. Otherwise, it will be rejected.
Inline -> Block: Do not place block level elements (div, h2, etc.) within inline elements (span, em).

JavaScript Rejections

Degradation: If an item requires JavaScript to work, you MUST provide an operable degraded version as well. For example, picture sliders should still be functional, at a minimal level, even when JavaScript is disabled. The practice of progressive enhancement should be employed to ensure that the script gracefully degrades in such a way that it remains minimally accessible to all users (or at least, the vast majority).
Complexity: The item is not of sufficient complexity or features to warrant approval. It’s important to us that items we approve are unique and do not offer more of what is already abundantly available online. It’s best to look at what scripts are already online and then possibly improve on what you find, possibly by adding unique features or even a superior implementation — anything to differentiate your item from what’s already available online.
Implementation: The item’s implementation is simply not up to the level of quality expected. There seems to have been only minimal thought given to application design. I can’t see much abstraction or any intuitive API for the buyer. It seems somewhat rushed and a buyer would find it difficult to customize this or integrate with it their own design and preferences. I suggest looking into design-patterns in JavaScript and abstraction.

PHP Rejections

Is it Unique: There are plenty of open source solutions available for nearly everything out there. We’re really looking for unique functionality, or items which provide a unique twist to an existing functionality.
Implementation: We expect code that’s top notch, secure and well commented. A clean application design and proper abstraction is implicitly expected.
Features: Less is more, sure; but when it comes to, say, a utility class, buyers are going to appreciate more features. There is such a thing as being too focused. Providing just a single, very simple feature isn’t going to get you far unless its implementation is spectacular.
Ease of Integration: The code must be easy for the purchaser to include in his existing projects relatively painlesslessly. Provide a more intuitive API, document your code better so that the user knows where he can hook into; provide separate config files to make it easier and provide a sample mini codebase to show them how it’s done.
Documentation: With code, documentation is king. Even for a very spartan utility class, we expect a well written, thorough help file expounding on the various methods it exposes, its signature and so forth. With a user script, take your time to create an installation guide and a quick start guide explaining all the features it provides. Please try to be as pictorial as possible in these guides. Our purchasers need not be tech savvy to use our scripts and being visual gets the point across quickly. Extra cookies for screencasts.
Lack of Market Prospects: This doesn’t happen often but, at times, we receive items that are generally well written, but have zero sales prospects. Before starting to write some code, please take a moment to think whether purchasers will pay money for such a functionality.

.NET Rejection Factors

Lack of Code, Binary, or Project: .NET is a rather unique category here at CodeCanyon in that .NET-based code can be compiled and distributed as a binary. However, CodeCanyon is a marketplace for selling code, and all submissions must include the source code, the compiled binary, and the project and/or solution of your component.
Failure to Follow Submission Instructions: Following the submission instructions is not only vital, but it saves time for everyone involved. They can be found here.
Design: A critical part of every piece of code is its design, and the folks at Microsoft authored a set of design guidelines for developers to follow to encourage consistency and predictability. It is expected to be designed according to the information found here.
Configuration: The best location for configuration settings is the web.config or app.config file – not in code. While the configuration section is useful for individual settings, components or libraries that need more complex configuration should incorporate the use of custom configuration sections. You can find a primer to custom configuration sections on Nettuts+.
Too General: You can find code freely available on the web. So, your item must distinguish itself from free code by providing features well beyond those free items.
Packaging: Non-visual components should be packaged as class libraries. Visual components (UI) should be packaged according to how they’re developed. ASP.NET user controls should be packaged as ASCX files (with code-behind if necessary), and UI controls developed as inheriting Control or WebControl should be packaged as class libraries.
Documentation: All public data types and their public members should be properly documented using XML documentation. This ensures that Intellisense gives the consumer appropriate information as they use your component in their project.

Other Rejection Reasons

Browser Testing: Have you tested your design in IE6 (optional), IE7, IE8, Firefox, Safari, Chrome, and Opera? While we do allow for alternative displays for older browsers — think simplified layout for IE6 users — your design must not break in any of these. If they do, your item will be rejected, with a request from the reviewer to make the necessary updates.
Documentation: Every template on CodeCanyon must include documentation to make the installation process as simple as possible for the purchaser. While you don’t have to teach the reader how to code, you should absolutely discuss any unique aspects of your template, which require further explanation.

We encourage you to use the documentation template, found here.

CodeCanyon: Soft Rejections

jeffrey — Thu, 08 Jul 2010 18:34:32 +0000

Each file uploaded to CodeCanyon goes through a strict reviewing process. Ideally, all your files will be accepted, though some may be rejected or soft-rejected. When a file is rejected outright, it’s completely removed from the reviewing queue. The only way to get it back is to fix the problem(s) and upload it again. Soft-rejections work a little differently than normal rejections.

The soft-rejection system was built for otherwise great files with minor issues preventing them from being accepted. For example, a file that would normally have been accepted, but the preview.swf was named incorrectly may be soft-rejected. In cases like this, the author would just need to fix the minor issue rather than re-uploading everything from scratch.

If your item has been soft-rejected, you’ll receive an email letting you know. Follow these steps to get your soft-rejected file re-reviewed.

Follow the link found in the email.
Click the edit button. The edit page is split up into two parts, “Update Description” and “Update Item and Tags.”
Make the changes outlined in the email.
1. If you change anything under “Update Description” like the description, published size, or resolution, be sure to click and return to the edit tab to complete the final steps.
  Note: Just clicking will not put your item in the soft-rejection queue!
2. Under “Update Item and Tags,” re-upload anything you’ve changed. Be sure to re-upload the preview, whether it changed or not.
In the notes to the reviewer, outline the changes you’ve made.
Click .

Once you’ve completed these steps, your file will enter the soft-rejection queue, which moves along more quickly than the normal queue.

CodeCanyon: How do I Upload a Video Preview to the CSS Category?

jeffrey — Tue, 15 Jun 2010 02:16:29 +0000

As items within the CSS category are highly susceptible to theft, we do not host live previews. Instead, authors are encouraged to upload 10-30 second video clips, which illustrate the effect of their items. This article will detail how to go about doing so.

Submit an .FLV Video

When submitting a new item to the CSS category on CodeCanyon, there will be an option to upload a short video, in the FLV format. However, most screencasting software do not offer FLV as an export option. In these cases, a free online service (no sign-ups), called Media Convert, will allow you to convert most video formats to FLV with the click of a button.

Screenr.com

It’s likely that you don’t own any screencasting software. If this is true, don’t worry; a free Twitter-based online service, called Screenr, allows you to easily record your screen, and upload the file to their servers for hosting. Once the files has been uploaded, there will be an option within the sidebar of the video page, which will allow you to download the MP4 file.

At this point, you can use the Media Convert service, listed above, to convert the file to FLV, accordingly. If you use this service, make sure that you set the “Video Quality” option to “1000.” Otherwise, the video will be a bit too blurry. Finally, when you upload your new awesome item to the CSS category, there will be an option to upload a short video clip, illustrating the effect of your item.

Alternatively: If you’re having trouble converting your file to the FLV format, your second option is to simply link to the Screenr.com hosted video from within the description section of the item page.

Tips on Recording Video Previews

Keep them short; otherwise, the potential buyer will lose interest. Try to limit your preview to 10-30 seconds in length.
You are not required to speak in your video. It’s encouraged; however, if you do not have a microphone available, your voice isn’t required.
Many authors record multiple videos for their items, including for the purposes of documentation. While only one video may be used for your featured preview, you can link to more from within your item’s description section, as well as your help file.
If you absolutely can’t figure out how to convert to an FLV video, you may upload an MP4, where the reviewer will then convert the video for you.

CodeCanyon: CSS Upload Instructions

jeffrey — Mon, 14 Jun 2010 19:41:43 +0000

Ensure You Are Using Acceptable Images/Extras:
It is up to you to ensure that all images/assets in your project are cleared for use. If necessary, you should contact the creator of the asset and ask them.

As an example, images from the stock photography site iStockPhoto are generally not usable in templates unless you have purchased an extended license for the item. In this instance you would report the extended license details in the comments section.

Please review this article for more information on acceptable assets.
Follow These Guidelines:
1. This category is exclusively for high-level CSS components, which go above and beyond what’s readily available around the web for free. DO offer convenience to your buyers; this includes multiple color schemes and layouts, if applicable.
2. DO NOT submit an item that doesn’t validate, excluding any CSS3 vendor-specific properties.
3. DO NOT submit an item if numerous similar offerings are already available in the CSS category.
4. Your item must not require JavaScript in order to function. This category is exclusively for CSS-specific items; however, if you only need to reference, for example, a script like Dean Edwards’ IE9.js, in order to force Internet Explorer to recognize advanced CSS properties, you may do so. Other than that, no custom JavaScript is permitted at this time.
5. DO provide documentation, which details exactly how to implement your item. We encourage you to use this template for your help file.
6. As CSS code is highly susceptible to theft, we do not host live previews. Instead, you should provide adequate screenshots of both your item and its code, and we encourage 10-15 second video clips, illustrating the effect of your item. Keep the length of the video below one minute (the shorter the better), and the video format must be .FLV. To learn more about how to create FLV video clips, refer here.
Create the Final Download File:
You should create a single ZIP file that contains the final files for download, any documentation and any auxiliary files such as extra images. This is the file that a user will get when they buy your item. Make it as complete as possible.

All Files Must Contain a Help File: All items sold on ThemeForest must contain documentation explaining how to customize, install and use the item. Especially for the components category, you must ensure that you’ve adequately detailed the necessary steps that need to be followed in order to implement your component into the buyer’s project.
Create a Preview Zip:
Include several screenshots which illustrate the functionality of your component. It’s essential that you provide plenty of images if you choose to forgo a live preview. Screenshots should be JPGs, should be no larger than 1200px in width, but can be any height. You can have up to 10 screenshots of the item, and each screenshot may have a description attached. Here’s how you set up the file:
1. Name each screenshot in sequence as number_Title.jpg. E.g. 1_Homepage.jpg, 2_Generalpage.jpg.
2. Create a .TXT file containing a few lines of descriptive text, with the same name as the screenshot. E.g. 1_Homepage.txt, 2_Generalpage.txt.
3. ZIP up the JPGs and TXTs together into a single ZIP file.
Create a 590px Wide Image Preview
This will be the featured image, when a user visits your item page. This is the first thing they see, so make sure that it’s effective. If you’re not a designer, use these PSD image templates, and substitute your item’s information.
Create a JPEG Thumbnail:
Finally create an 80px x 80px JPG thumbnail for your file. The thumbnail should represent your item in some way.
Upload your files to CodeCanyon!

CodeCanyon: Plugins Upload Instructions

jeffrey — Fri, 09 Apr 2010 06:23:55 +0000

Ensure You Are Using Acceptable Images/Extras:
. It is up to you to ensure that all images/assets in your project are cleared for use. If necessary, you should contact the creator of the asset and ask them.

When you upload the item, there is a field titled “Comments for Reviewer”. Please list any external assets you’ve used and where you obtained each one.

As an example, images from the stock photography site iStockPhoto are generally not usable in templates unless you have purchased an extended license for the item. In this instance you would report the extended license details in the comments section.

Please review this article for more information on acceptable assets.
Follow These Guidelines:
1. DO NOT borrow code from similar plugins.
2. DO code in such a way that makes the integration process as simple as possible for the buyer.
3. DO NOT assume that the buyer has any coding knowledge.
4. DO NOT upload plugins which are similar to items widely available for free around the web.
Create the Final Download File:
You should create a single ZIP file that contains the final files for download, any documentation and any auxiliary files such as extra images. This is the file that a user will get when they buy your item. Make it as complete as possible.

All Files Must Contain a Help File: All items sold on ThemeForest must contain documentation explaining how to customize, install and use the item. Especially for the components category, you must ensure that you’ve adequately detailed the necessary steps that need to be followed in order to implement your component into the buyer’s project.
Create a Preview Zip:
Include several screenshots which illustrate the functionality of your component. It’s essential that you provide plenty of images if you choose to forgo a live preview. Screenshots should be JPGs, should be no larger than 1200px in width, but can be any height. You can have up to 10 screenshots of the item, and each screenshot may have a description attached. Here’s how you set up the file:
1. Name each screenshot in sequence as number_Title.jpg. E.g. 1_Homepage.jpg, 2_Generalpage.jpg.
2. Create a .TXT file containing a few lines of descriptive text, with the same name as the screenshot. E.g. 1_Homepage.txt, 2_Generalpage.txt.
3. ZIP up the JPGs and TXTs together into a single ZIP file.
Create a 590px Wide Image Preview
This will be the featured image, when a user visits your item page. This is the first thing they see, so make sure that it’s effective. If you’re not a designer, use these PSD image templates, and substitute your item’s information.
Create a JPEG Thumbnail:
Finally create an 80px x 80px JPG thumbnail for your file. The thumbnail should represent your item in some way.
Link to a Live Preview
Though this is not required, we highly recommend that you link to a live preview that demonstrates your plugin’s functionality on your own server. In general, we’ve found that not doing so can hinder sales substantially. When uploading, there will be an option to paste in a url to the preview, should you decide to do so.
Upload your files to CodeCanyon!

How Does CodeCanyon Work?

jeffrey — Wed, 02 Dec 2009 06:37:21 +0000

CodeCanyon is an Envato Marketplace. At CodeCanyon, you can purchase and sell scripts and components for a variety of languages and frameworks, currently including JavaScript, PHP, ASP.NET, and Java. Items are priced between $3 and $25; we review complexity, quality, and overall appeal when determining the specific value to assign to an item.

Finding and Buying Items

There are lots of ways to find the items you want:

Category List – Browse CodeCanyon’s extensive category list here.
Keyword Search– Access the search field on the top right of any page.
Popular Files – Check out our weekly summary of the most popular items
Collections – Browse our user-compiled item collections on a variety of themes
Featured Files – Handx-picked by our site editors each week
Top Authors – Look through the portfolios of our top authors

You can buy items by depositing cash. Once you have money in your account, just click the Purchase button in the top-right of any item’s description page. You’ll be taken from there to a file-download dialog. Download your purchased items at any time by going to your Account > Downloads page.

Need help buying? Read our Step by Step Guide to Purchasing Items

Join Envato, Join a Community

CodeCanyon is more than just a place to find helpful components, it’s a growing community! You can hear from authors, ask questions in the forums, and comment on items.

At CodeCanyon we like to say that it is this community who really owns the site and we do our best to make sure they get the most out of it by providing not just great selling facilities but also interactivity, news, competitions and whatever else we can dream up!

Plus CodeCanyon is just one of a whole set of Envato Marketplaces. Signing up for an account on CodeCanyon will instantly give you access to the whole Envato network.

Item Support and FAQs

All items for sale on CodeCanyon are reviewed to ensure they are in good working order and are easy to use. Further item support such as alterations/enhancements is at the discretion of each author. You’ll find that the CodeCanyon forum is also a good place to find help for using or modifying items.

Want to Sell Items or Join the Referral Program?

Envato Marketplace authors make 50%-70% on every item sold. Refer new users and receive a 30% commission from their first Cash Deposit! Go here to get started:

Site Support

There is a lot of useful information in the marketplace wiki. If you need any help or any answers that aren’t in the wiki, support is open from 9am to 5pm Monday to Friday, Australian Eastern Standard time. Support tickets will be answered within two working days.