Initializing... drag & drop files here
Supports: NEF
A .nef is a Nikon RAW still — unprocessed sensor data. An .eps is an Encapsulated PostScript file, the format print workflows and older page-layout software use to place artwork. This conversion develops the RAW and embeds the resulting pixels inside a PostScript wrapper. It does not trace, vectorise or redraw anything: what comes out is your photograph, in a PostScript envelope, at one point per pixel. That envelope is uncompressed and written as 7-bit ASCII, which makes these files startlingly large — so it is worth knowing the numbers before you convert.
| Property | Value |
|---|---|
| Full name | Nikon Electronic Format — Nikon's proprietary RAW format |
| What it stores | All the image information captured by the camera's sensor, plus metadata about the body, settings and lens |
| Processing state | Unprocessed. Per Nikon, white balance, hue, tone and sharpening are not applied in-camera — they are retained as instruction sets inside the file |
| Typical bit depth | 12-bit or 14-bit per channel |
| Nature of the image | Raster. A grid of sensor samples, with no paths, curves or text objects |
| Preview | NEF is one of two RAW extensions with a dedicated thumbnail path in our uploader, so the on-page preview normally renders |
We converted a test frame and read the resulting file's header. These are the values our pipeline writes, not generic format trivia:
| Header field | Value written | What it means for you |
|---|---|---|
%!PS-Adobe-3.0 EPSF-3.0 |
— | A conforming Encapsulated PostScript file |
%%LanguageLevel |
1 |
PostScript Level 1 — the most compatible level, and the one without the compression filters later levels added |
%%DocumentData |
Clean7Bit |
The image data is written as printable ASCII, not binary — roughly two characters per byte of pixel data |
%%BoundingBox |
0 0 6000 4000 for a 6000 × 4000 photo |
One pixel becomes one PostScript point. At 72 points per inch that box is about 83 × 56 inches |
%%Pages |
1 |
A single page. Frame 0 only — multi-frame inputs are not carried over |
| Image content | Embedded raster | Your developed photograph. Nothing is converted to vector paths |
.nef onto the page or click "+ Add Files". Several Nikon RAW files can be queued and converted with the same setting..eps. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.| Source pixels | Measured EPS size |
|---|---|
| 1920 × 1080 (2.1 MP) | 12,606,816 bytes — about 12.6 MB |
| 6000 × 4000 (24 MP) | 145,851,856 bytes — about 146 MB |
The relationship is close to linear in pixel count, because there is essentially no compression: three bytes of RGB per pixel, each written as two ASCII hex characters, plus line breaks and a small PostScript prologue. That works out at about 6.1 bytes per pixel, so a 45-megapixel Nikon frame at 8256 × 5504 lands near 275 MB. If that is impractical, drop Resolution Percentage — it is the only control that changes the outcome.
No. This is the most important thing to understand about raster-to-EPS conversion anywhere, not just here. EPS is a PostScript container, and PostScript can describe both vector paths and embedded raster images. A photograph has no paths to describe — it is a grid of samples — so the converter embeds it as a raster image inside the PostScript wrapper. Scaling the result up in a layout program enlarges pixels exactly as it would with a JPEG. If you genuinely need vector output you need a tracing tool and an image with hard, flat-colour edges; photographs are not suitable candidates, and RAW files are not accepted as tracing input at all.
Two reasons compound. First, the file is uncompressed: PostScript Level 1 has no built-in image compression filter, so every pixel's red, green and blue values are written out in full. Second, the data is ASCII rather than binary — the header declares Clean7Bit — which means each byte becomes two printable hex characters. Together that is roughly six characters per pixel. Our measured 24-megapixel conversion came out at about 146 MB from a source RAW a fraction of that size.
No, and this is unusual even among our image targets. EPS is the one image output with no pixel-dimension control at all — no width, no height, no width × height, no resolution presets. Only Keep original and Resolution Percentage render. The DPI selector does not appear either, because the conversion pins the density at 72 pixels per inch so that one pixel maps to exactly one PostScript point. Scale with the percentage control, or place and resize the EPS in your layout application.
Whatever the bounding box says, and the bounding box is your pixel dimensions read as points. Our 6000 × 4000 test frame produced %%BoundingBox: 0 0 6000 4000, which at 72 points per inch is roughly 83 by 56 inches — far larger than any page. Almost every layout program lets you scale a placed EPS, so this is a nuisance rather than a blocker; just expect to shrink it after placing, and remember that scaling down effectively raises the print resolution.
No. Microsoft's own picture-insertion guidance states plainly that EPS files can no longer be inserted into Office documents. If Office is your destination, convert to NEF to PNG for a lossless copy or NEF to JPG for a small one — both insert without complaint. EPS remains useful for print and prepress workflows and for older page-layout software, which is where it still earns its place.
Level 1, as declared by the %%LanguageLevel: 1 comment in the file we produced. That is the most broadly compatible choice — a Level 1 EPS is readable by essentially anything that has ever understood PostScript, including elderly RIPs and imagesetters. The cost is exactly the file size described above: the compression filters and richer colour spaces that arrived with Levels 2 and 3 are not used, so the image data is stored in the plainest possible form.
They are spent at the render step. Nikon retains white balance, hue, tone and sharpening as instruction sets rather than applying them to the sensor data, which is what makes RAW re-editable. To write an EPS the pipeline must demosaic the sensor samples and commit to one interpretation, producing ordinary 8-bit-per-channel image data. Keep the .nef as your master. If you want a still that survives further editing, NEF to TIFF preserves considerably more.
No. The conversion strips metadata, so camera model, lens, exposure settings and any embedded JPEG preview do not travel into the EPS. Some applications will therefore show a grey placeholder box rather than a thumbnail when the file is placed, and render the actual image only at print or export time — that is normal EPS behaviour when no preview is embedded, not a sign the file is broken.
Only if a print shop, prepress workflow or older layout application specifically asks for it. For everything else the answer is a normal raster format: NEF to TIFF is the usual print-industry choice and carries 16-bit data with real compression options, NEF to PNG is lossless and universally viewable, and NEF to JPG is small enough to email. The NEF converter hub lists every target we support from Nikon RAW.