Magnific (formerly Freepik) Contributor Guide: Requirements, CSV Metadata, AI Images and Best Practices

Magnific.com (formerly Freepik) is one of the largest creative asset platforms, and getting your content approved means understanding its technical requirements, metadata rules, and a handful of behaviors that the official documentation never spells out. This guide walks through everything a contributor needs: file requirements by type, the review process, contributor levels, keyword and title rules, the CSV workflow, AI content policy, and the rejection reasons that trip up most submissions. It also documents the file-naming and deduplication behavior we mapped through direct testing, which is critical for anyone uploading in bulk.

1. Getting Started: Your First Submission

To become a Magnific contributor you sign up for a contributor account, log in, and go to the Upload content section.

Your first submission is a qualification test:

Upload between 150 and 200 files.
All files in a test submission must use the same format (all photos, all vectors, or all PSD).
Fill in the metadata, title, and the “Created with artificial intelligence” flag where applicable.
Review carefully before submitting. Once a file is under review you cannot edit or delete it.

If you are not accepted, you can try again after one month.

2. Technical Requirements by File Type

Magnific accepts three content types: Photos (JPG), Vectors (EPS), and PSD files. Note that PNG and video are not part of the contributor upload flow.

Photos (JPG)

Property	Requirement
Format	JPG / JPEG
File size	1.5 MB min, 250 MB max
Dimensions	2,000 px min, 10,000 px max
Resolution	4 MP min, 100 MP max
Color mode	sRGB, Adobe RGB, ProPhoto RGB
Compression	Lowest possible (preserve maximum information)

Photos must be sharp, free from watermarks or logos, and free from excessive editing.

Vectors (EPS)

A vector file must be uploaded together with a JPG preview that has the same name.

Property	Requirement
Vector format	EPS (Adobe Illustrator CC)
Vector file size	0.5 MB min, 80 MB max
Color mode	RGB
Preview format	JPG
Preview dimensions	2,000 px min, 10,000 px max
Preview resolution	4 MP min, 100 MP max

Vectors must have clean paths, organized and named layers, properly grouped elements, and no unnecessary rasterized effects. Avoid live tracing except in the specific cases described later.

PSD Files

A PSD must be uploaded with a JPG preview. Requirements vary by PSD subtype.

PSD mockups and graphic elements

Color mode: RGB (profiles: sRGB, Adobe RGB, ProPhoto RGB, or P3)
Version: CC
File size: 250 MB max
Resolution: 4 MP min, 100 MP max
Dimensions: 1,000 px min, 5,000 px max
Preview JPG: 2,000 px min, 10,000 px max

PSD templates (for print)

Color mode: CMYK
Color profile: Coated FOGRA27
Version: CC
Resolution: 150 dpi min, 300 dpi max
Dimensions: must match standard paper sizes (business card 85 x 55 mm, flyer A5, letterhead A4, poster A3, and so on)

PSDs must be fully editable, never flattened, with layers neatly named in English. All fonts must be free for commercial use.

A note on conflicting numbers: Magnific’s own documentation lists slightly different limits in different places (for example a rejection table that caps photos at 80 MB while the upload bar and content requirements allow 250 MB, and preview resolution stated both as a pixel range and as a megapixel range). When in doubt, stay comfortably inside the stricter value: a photo of at least 2,000 px on the short side, between 1.5 MB and around 80 MB, and under 100 MP will satisfy every version of the rules.

3. Upload Methods and Contributor Levels

Magnific offers two upload methods, and access to them depends on your contributor level.

Web upload (manual): available to all levels. Upload one or many files and complete the required fields.

FTP upload: for large volumes, available only to Level 3 contributors. You connect with an SFTP client such as FileZilla using the credentials shown in your dashboard:

Host: sftp://contributor-ftp.magnific.com
Port: 60022
User: your contributor username
Password: retrieved with the “Get password” button

After transferring files to the FTP server you click Synchronize FTP in the dashboard to import them.

Contributor Levels

Level	Upload volume	Method	To progress
Level 1	150 to 200 assets (qualification test, same format)	Web	Get your first assets approved to reach level 2
Level 2	1 to 200 assets	Web	Reach 500 published assets to reach level 3
Level 3	1 to 200 assets	Web or FTP	–

Upload Limits

Monthly limit: 200 files per month per account. If you have uploaded 120 this month, you can add only 80 more until the limit resets next month.
Upload folder limit: the folder holds a maximum of 200 files at a time. You cannot add more until some are sent for review or removed.

4. Checking File Status and Unpublishing

After upload, files go through review. Allow up to 25 working days. In the My files section each asset shows one of three states:

Under review
Approved (live on the platform)
Rejected (reasons appear in the file’s comments)

To remove published content, go to Published Content, select the file(s), and click Unpublish asset. Removal and deindexing can take up to 24 hours. You can unpublish one or many files at once, and republish later by uploading again. You cannot edit published content; you can only add model releases or unpublish it.

5. Titles and Keywords

Metadata drives discoverability, so this is where careful work pays off.

Titles

Write one clear, concise sentence that answers who, what, when, and where. The title should describe the concept and theme of the resource. The maximum length is 100 characters.

Common title mistakes to avoid:

Too short or too long
Wrong references that do not describe the actual content
Mentioning the file type (no “EPS10”, “JPG”)
Spelling and grammar errors
Unnecessary numerals or dates (acceptable only when contextual, such as “4th of July”)
Special characters or symbols

Keywords

They suggest to use 15 to 20 well-chosen keywords, but 50 is the maximum number. Remember that for AI generated content, the _ai_generated keyword must be added, reducing the number of relevant keywords to 49
All keywords in English (proper nouns excepted).
Describe only what you can see in the resource or its concept: subject, setting, colors, style, mood, emotion.
Include relevant synonyms and variations.

Common keyword mistakes to avoid:

Repetition and exhaustive color listings
Misleading campaign tags or hashtags (no “#summer”, no “summeredition”)
Generic filler (“cool”, “nice”, “fun”, “lorem ipsum”)
File types (“EPS10”)
Special characters

Worked example. For a summer pool sale poster:
Good title: “Promotional Poster Pool Days Forever with Summer Theme”
Good keywords: summer, pool, discount, promotional poster, flyer, colorful design, floaties, tropical leaves, vacation, relaxation, sale, promo code, creative typography, pool days, tropical, seasonal campaign
Weak title: “Pool Days Forever” (just the on-poster text, no concept)
Weak keywords: poster, internet, cool, lorem ipsum, nice, image, blue, pink, summeredition, web, EPS10, #summer (generic, color-spam, hashtags, file type)

Tip: Building precise 15 to 20 keyword sets by hand for hundreds of files is slow and inconsistent. Photokeyworder.ai generates accurate, platform-ready titles and keywords from the image itself, so your metadata describes what is actually in the file and stays within Magnific’s rules.

6. Creating a CSV File to Upload Metadata

Instead of typing metadata by hand, you can upload a CSV that describes all your files at once, either through the FTP server or directly in the contributor panel’s Upload section.

Structure

Magnific uses the semicolon (;) as the field separator, and the comma (,) to separate individual keywords inside the keyword field. This is important: do not use a comma as the field separator, or your file will not parse correctly.

Field order:

File name; Title; Keywords; Prompt (if AI-generated); Model (if AI-generated)

Examples:

"beautiful-sunset.jpg"; "Beautiful sunset"; "sunset,sun,summer,beach,mountain"; "Beautiful sunset on the beach in summer"; "Midjourney 5"
"abstract-background.jpg"; "Abstract polygonal background"; "abstract,polygonal,poly,polygon,polygons,low poly"

Saving the CSV correctly

Microsoft Excel: save as CSV (MS-DOS).
Google Sheets: enter the data, then export as CSV.
OpenOffice Calc: File > Save As > Text CSV (.csv), set the field separator to semicolon (;).

When formatting, set the field delimiter to semicolon and, if your tool offers them, enable options such as “always overwrite template when generating standard CSV” and “replace NULL values with an empty value”. Then upload the finished CSV to the FTP server or the contributor panel.

Tip on file names in the CSV: From our testing, Magnific seems to apply the same name normalization to the file names listed inside the CSV as it does to the uploaded files themselves, then matches them. In practice you do not have to manually rewrite your CSV file names to match the platform’s transliterated versions: the system reconciles them for you. That said, the safest path remains to use clean file names from the start (see the next section), which removes any ambiguity regardless of how the matching is performed.

7. File Naming and Deduplication: What the Documentation Does Not Tell You

This is the part no official guide covers, and it matters enormously for bulk uploads. We ran a series of tests on how Magnific rewrites file names, and the behavior is consistent across both web and FTP uploads.

The normalization pipeline

When you upload a file, Magnific rewrites the base name (everything before the final extension) through these steps, in this order:

Extension is preserved. Only the final .ext is kept as the extension; the rest of the name is normalized.
Accents and diacritics are stripped to plain ASCII (è, é become e; ì becomes i; ù becomes u; à becomes a; ò becomes o). Unicode is normalized first, so a precomposed name (NFC) and a decomposed name (NFD) produce the identical result. There is no precomposed-vs-decomposed bug here.
Spaces are cleaned: multiple consecutive spaces collapse to one, and leading and trailing spaces are trimmed.
Punctuation and most symbols become a hyphen (-): this includes , . ; : ! ' # @ ^ & $ + = [ ] ( ) £ and similar.
Hyphens are cleaned: consecutive hyphens collapse to one, and leading and trailing hyphens are trimmed.
Case is preserved: uppercase and lowercase are kept exactly as typed (the system does not lowercase your names).

Confirmed examples

You upload	Magnific stores
`csv test con spazi.jpg`	`csv test con spazi.jpg`
`csv Test-001, misto.finale.jpg`	`csv Test-001- misto-finale.jpg`
`csv,virgola,test.jpg`	`csv-virgola-test.jpg`
`csv.test.con.punti.jpg`	`csv-test-con-punti.jpg`
`csv_test_001.jpg`	`csv_test_001.jpg`
`CSV_Test_Maiuscole.jpg`	`CSV_Test_Maiuscole.jpg`
`-test--trattino--inizio--fine-.jpg`	`test-trattino-inizio-fine.jpg`
`caffèéìùàò NFC/NFD.jpg`	`caffeeiuao NFC/NFD.jpg`
`test spazi multipli .jpg`	`test spazi multipli.jpg`
`test-special[(!'#@^&$€;+,£%=2.jpg`	`test-special-€-%-2.jpg`

Two odd survivors

Almost every symbol becomes a hyphen, but two characters slip through the filter and are kept verbatim: the euro sign (€) and the percent sign (%). This is not a “currency symbols are kept” rule, because £ and $ are converted. It is an inconsistent whitelist. Both € and % are problematic in FTP paths and URLs, so even though they technically pass, you should avoid them.

A second subtlety: spaces are cleaned before symbols are converted, so in rare cases a name can end up with a stray space before the extension (when a trailing symbol “shields” a space during trimming and only later becomes a hyphen that gets removed). It is an edge case, but it confirms the order of operations above.

Deduplication: collisions are decided on the normalized name

Because different originals can normalize to the same string (caffè.jpg and caffe.jpg both become caffe.jpg), Magnific treats them as duplicates even though the images are different. Matching is on the name only, not on content.

Web upload: you get an interactive warning, “A file with this name already exists. Would you like to replace it?”, with a side-by-side comparison of the new and existing file (date and size). You choose Skip (keep the existing one and rename your new file) or Replace (overwrite). Choosing Replace here would silently discard a perfectly valid, distinct image, so be careful.

FTP upload: there is no interactive dialog. The first file written wins, and any later file that normalizes to the same name fails server-side. In some cases, we’ve noticed that the first file was imported two times with the same name, generating a duplicate. Files with some special characters can’t be uploaded at all (for example, “test-special[(!'#@^&$€;+,£%=2.jpg” couldn’t be uploaded). For Level 3 contributors pushing large batches through FileZilla, this means a single symbol difference can cause silent file loss.

The safe naming rule

To make the name you write identical to the name Magnific stores, and to eliminate every collision and matching risk:

Use only a-z, A-Z, 0-9, with single _ or - as separators. No spaces, no accents, no symbols (including € and %), and no separator at the start or end of the name. Make sure every name is unique after these rules are applied.

8. Image Rights Releases

When your photos show recognizable people or private property, you must provide the appropriate signed release, uploaded as a separate file alongside the photo.

Model release: required for every recognizable person in the image, primary or incidental. For anyone under 18, the form must be signed by a parent or legal guardian.
Property release: required for private property, including buildings and trademarked locations, when used commercially.
Animals: wild animals are acceptable if not endangered or harmed; pets require a property release from the owner for commercial use.

Releases must be legible, complete, unedited, and signed by all parties. An image with a recognizable person and no valid release will be rejected.

9. AI-Generated Content

Magnific accepts AI-generated photos, vectors, and PSDs, with conditions.

Tag every AI file. Use the “Created with artificial intelligence” button in the Upload section, or add _ai_generated tag in your keywords.
Visual integrity: no malformed anatomy (extra fingers, deformed bodies), no distorted or unreadable text, no flat or low-detail textures.
No prompt spam: do not upload many near-identical results from the same prompt. Each file must offer distinct value.
AI must meet the standard format rules for its type: AI photos that simulate photography must satisfy all photo guidelines (correct anatomy, clean detail); AI vectors must be individually selectable, avoid live trace, and meet vector rules; AI PSDs must have working smart objects, clean cutouts, and proper layer organization.
Releases still apply: recognizable people or private locations in AI photos require model or property releases.

10. Vector, PSD, and Photo Best Practices

Vectors

Live trace is allowed only for traditional-media textures (watercolor, ink, pencil, charcoal) where it adds real value. Never vectorize flat illustrations, logos, or UI elements through tracing. When used, prefer stacked tracing (layered shapes, more accurate) over cutout (puzzle-fit shapes, can lose detail), keep groups logical, and remove stray anchor points.
Composition: distribute elements evenly, keep clear separation, use consistent margins, and build a clear visual hierarchy. Do not crowd the edges of the artboard.
Single elements: a lone icon or pictogram is often rejected on its own. Group it into a themed pack to add value.
No elements outside the artboard, and all text must be editable (outlining is allowed only when the font shape is essential, an effect prevents editability, or the font is custom-made by the author).

PSD

Editable area must show a realistic design or text. A flat color or empty placeholder in the editable zone is rejected.
No embedded images of any kind inside the PSD, on any layer, including inside smart objects or hidden via layer effects. Photos may appear only in the JPG preview, and then only if free for commercial use, with the label “IMAGE NOT INCLUDED” clearly visible. Missing that label is its own rejection reason.
Layers organized and grouped, each editable element in its own group, named in English (for example “Totebag”, “Background Texture”).
Naming conventions: smart object group “Place your design here (Double click to edit)”; color adjustment layers “Color T-shirt”; scene effect layers “FX light”, “FX shadow”, “FX vignette”.
Masks linked to their smart object (unlinked only for scene creators), and a blue label applied to every user-editable element (smart objects, color layers, FX layers that affect the look).
Graphic elements: transparent backgrounds, clean edges with no halos or leftover artifacts, previewed on white or a checkerboard pattern.

Photos

Aim for one clear concept per image, neutral white balance, purposeful depth of field, level horizons, and ethnic diversity in representation. The review team rejects:

Upscaling artifacts and low resolution
Chromatic aberration, JPEG compression artifacts, excessive sharpening halos, chromatic noise
Aggressive filters, excessive vignetting, oversaturation, harsh black-and-white conversions
Unintentional blur, motion blur with no clear point of focus
Under- or overexposure, flat lighting, excessive contrast
Unintentional Dutch angle (tilted horizon)

11. Bad Practices That Can Suspend Your Account

Magnific strongly discourages the following. Serious cases can lead to account suspension or termination, withheld earnings, and legal action.

Artificial downloads: paying or arranging for downloads that are not genuine is forbidden.
Trademark and copyright: no logos, brand names, or protected characters; no recreated or “inspired” designs too similar to registered works; no third-party elements even under CC0. Iconic shapes can be protected even with the logo removed (Polaroid frames, the VW T1 van, LEGO blocks). Architecture and urban art only when public domain, not the main subject, and compliant with local Freedom of Panorama. Current social media logos (TikTok, Instagram, X) are allowed if up to date. Currency must never appear flat, scanned, or in its entirety.
Plagiarism: reusing or modifying another author’s elements is plagiarism and leads to a permanent ban. Even a heavily “inspired” design that mimics composition, style, or concept can qualify.
Repeated submissions: the same image (accepted or rejected) cannot be resubmitted. Rotations, flips, reframes, color changes, and position changes do not count as original. For non-editable numbered designs, a small range (typically 1 to 10) is allowed; if the number is editable, multiple versions are not.
Outdated content: a design with a specific year must reflect the current year (past dates like “Happy New Year 2022” are rejected). Near year-end you may begin submitting next-year content.
Outdated or branded devices: devices should be recent (one to two years) and generic in design, with no brand-specific traits. Older devices only when essential to a retro concept.
Sensitive content: no content that promotes inappropriate behavior, violence, drug use, hate, or that objectifies people. Nudity only with clear artistic, medical, or editorial intent, never gratuitous, and never with minors or anyone who could be mistaken for one. Political, cultural, and territorial themes must stay neutral; maps and flags must follow internationally recognized standards.
Prohibited elements: no signatures, watermarks, author identifiers, references to Magnific, camera or AI watermarks, QR codes, or working links and personal data.
Multiple accounts: one active account per contributor unless Magnific grants written consent.

12. Reasons for Rejection at a Glance

General reasons that apply to all types:

Unauthorized attribution, trademark or copyright issues, plagiarism, sensitive content
Similar or duplicate content, outdated content
Incorrect dimensions or size, errors or rendering glitches in the file
Low-quality or pixelated preview, spelling and grammar mistakes, incoherent typography
Poor composition, distortions, functionality problems
Files without metadata: you have 10 days to add the required title, tags, and category, after which the file is automatically rejected (re-check your CSV or FTP upload for empty fields)
Missing “image not included” label

Photo-specific: improper post-production, blur or lack of sharpness, lighting problems, missing model release.

Vector-specific: image embedded in EPS, detail lost through image trace, single icon not in a set, unbalanced color palette, elements outside the artboard, non-editable text.

PSD-specific: image included in the PSD, disorganized or unnamed layers, bad cutouts.

Invalid or incomplete uploads are also a common failure: an EPS without its matching JPG preview, a preview whose name does not match the vector, a corrupted file, or a file that is not actually a valid EPS or JPG despite its extension. The name-matching requirement is exactly why the normalization rules in Section 7 matter: confirm that your vector and its preview still share the same name after normalization.

Final Checklist Before You Submit

File type, size, dimensions, resolution, and color mode all within range
EPS or PSD paired with a correctly named JPG preview (matching name after normalization)
Clean, unique, ASCII-only file names with single _ or - separators
Relevant English keywords, a clear descriptive title no longer than 100 characters, no file types or hashtags
AI files tagged, with prompt and model where relevant
Releases attached for recognizable people and private property
No embedded images in PSD/EPS; “IMAGE NOT INCLUDED” label where needed
Layers organized and named in English, everything fully editable
CSV uses ; as the field separator and , between keywords

Get the technical details right and your approval rate climbs, your files stay matched to their metadata, and you avoid the silent failures that catch out bulk uploaders. For the metadata itself, Photokeyworder.ai keeps your titles and keywords accurate, relevant, and within Magnific’s guidelines, file after file.